MCP server
by tao12345666333
Manage cloud infrastructure and services easily with Civo. Automate instance lifecycle, Kubernetes, and networks via pow
Manages Civo cloud infrastructure including instances, networks, and Kubernetes clusters through their API. Lets you provision and control cloud resources directly from your MCP client.
Civo is a community-built MCP server published by tao12345666333 that provides AI assistants with tools and capabilities via the Model Context Protocol. Manage cloud infrastructure and services easily with Civo. Automate instance lifecycle, Kubernetes, and networks via pow It is categorized under cloud infrastructure.
You can install Civo in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Civo is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Civo is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Civo benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Civo is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Civo for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Civo is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Civo benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Civo into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired Civo into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Civo against two servers with overlapping tools; this profile had the clearer scope statement.
Civo has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 60
An MCP server implementation that integrates with the Civo cloud platform API, providing capabilities to manage cloud instances, networks, and Kubernetes clusters.
<a href="https://glama.ai/mcp/servers/@tao12345666333/civo-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@tao12345666333/civo-mcp/badge" alt="Civo Server MCP server" /> </a>Or you can also view the details of each step through this public Amp thread.
First, install the Civo MCP server with your client. A typical configuration looks like this:
{
"mcpServers": {
"civo": {
"command": "npx",
"args": ["civo-mcp"],
"env": {
"CIVO_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
<details>
<summary><b>Install in VS Code</b></summary>
You can install the Civo MCP server using the VS Code CLI:
# For VS Code
code --add-mcp '{"name":"civo","command":"npx","args":["civo-mcp"],"env":{"CIVO_API_KEY":"YOUR_API_KEY_HERE"}}'
After installation, the Civo MCP server will be available for use with your GitHub Copilot agent in VS Code.
</details> <details> <summary><b>Install in Ampcode</b></summary>Follow Amp MCP documentation. Use following configuration:
"amp.mcpServers": {
"civo": {
"command": "npx",
"args": ["civo-mcp"],
"env": {
"CIVO_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
</details>
<details>
<summary><b>Install in Claude Code</b></summary>
Use the Claude Code CLI to add the Civo MCP server:
claude mcp add civo npx civo-mcp
Then set your API key as an environment variable:
export CIVO_API_KEY="your_api_key_here"
</details>
<details>
<summary><b>Install in Gemini CLI</b></summary>
Follow the MCP install guide, use following configuration:
{
"mcpServers": {
"civo": {
"command": "npx",
"args": ["civo-mcp"],
"env": {
"CIVO_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
</details>
<details>
<summary><b>Install in Cursor</b></summary>
Go to Cursor Settings → MCP → Add new MCP Server. Name to your liking, use command type with the command npx civo-mcp. You can also verify config or add command like arguments via clicking Edit.
{
"mcpServers": {
"civo": {
"command": "npx",
"args": ["civo-mcp"],
"env": {
"CIVO_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
</details>
<details>
<summary><b>Install in Windsurf</b></summary>
Follow Windsurf MCP documentation. Use following configuration:
{
"mcpServers": {
"civo": {
"command": "npx",
"args": ["civo-mcp"],
"env": {
"CIVO_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
</details>
<details>
<summary><b>Install in Claude Desktop</b></summary>
Follow the MCP install guide, use following configuration:
{
"mcpServers": {
"civo": {
"command": "npx",
"args": ["civo-mcp"],
"env": {
"CIVO_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}
</details>
create_instance
hostname (string): Fully qualified domain namesize (string): Instance size (e.g. 'g2.small')template_id (string): Disk image IDcount (number, optional): Number of instances to create (default: 1)region (string, optional): Region identifier (default: 'LON1')list_instances
region (string, optional): Filter by regionpage (number, optional): Pagination page (default: 1)per_page (number, optional): Results per page (default: 20)reboot_instance
id (string): Instance IDregion (string): Region identifiershutdown_instance
id (string): Instance IDregion (string): Region identifierstart_instance
id (string): Instance IDregion (string): Region identifierresize_instance
id (string): Instance IDsize (string): New instance sizeregion (string): Region identifierdelete_instance
id (string): Instance IDregion (string): Region identifierlist_disk_images
region (string, optional): Region identifierget_disk_image
id (string): Disk image IDregion (string, optional): Region identifierlist_networks
create_network
label (string): Network labelregion (string, optional): Region identifierrename_network
id (string): Network IDlabel (string): New network labelregion (string, optional): Region identifierdelete_network
id (string): Network IDregion (string): Region identifierlist_kubernetes_clusters
region (string, optional): Filter by regionpage (number, optional): Pagination pageper_page (number, optional): Results per pagecreate_kubernetes_cluster
name (string): Cluster nameregion (string): Region identifiernetwork_id (string): Network ID for the clusternodes (number): Number of worker nodesnode_size (string): Size of each nodekubernetes_version (string): Kubernetes versiondelete_kubernetes_cluster
id (string): Cluster IDregion (string): Region identifierlist_kubernetes_versions
list_sizes
list_regions
CIVO_API_KEY: Your Civo API Key (required)NODE_ENV: Set to production to disable debug logging (optional)Contributions are welcome! Please follow these steps:
git checkout -b feature-namenpm run test:cigit clone https://github.com/tao12345666333/civo-mcp.git
cd civo-mcp
npm install
npm run build
# Run all tests
npm test
# Run tests in watch mode
npm run test:watch
# Generate coverage report
npm run test:coverage
This MCP server is licensed under the MIT License. See the LICENSE file for details.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.