civo

The Civo MCP Server provides a set of tools to manage Civo cloud resources directly through an MCP client. It supports instance management (create, list, start, stop, reboot, resize, delete), disk image operations, network management, and Kubernetes clusters. You can create and configure cloud instances, view and use available disk images, manage private networks, and deploy or maintain Kubernetes clusters, including listing available versions. The server exposes a standardized set of commands that your MCP client can invoke, with parameters such as region, size, and templates to tailor resources to your environment. To start, you configure the server with your Civo API key and then use the client’s capabilities to perform common cloud operations without leaving your MCP workflow.

Prerequisites:

• Node.js 20 or newer installed on your machine
• An MCP client or environment (e.g., VS Code MCP extension, Ampcode, Claude Code, Gemini CLI, Cursor, Windsurf) capable of loading MCP servers
• A Civo account with a valid API key

Installation steps:

1. Obtain the MCP server configuration snippet for Civo from the repository README or server page. The configuration typically looks like:

{
  "mcpServers": {
    "civo": {
      "command": "npx",
      "args": ["civo-mcp"],
      "env": {
        "CIVO_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

2. Save the configuration in your MCP client configuration file (e.g., settings or mcp.json) as shown above. Replace YOUR_API_KEY_HERE with your actual Civo API key.

3. Install and run the MCP server via your client. For example, in a terminal environment that supports npx, you can start the server with:

npx civo-mcp

4. In your MCP client, connect to the newly configured server named (for example) civo and begin issuing commands such as create_instance, list_instances, create_network, or create_kubernetes_cluster. Ensure your API key is valid and that the client has network access to Civo APIs.

Tips and considerations:

• Always store your CIVO_API_KEY securely and do not commit it to version control.
• If you encounter rate-limit issues, review the server's rate limiting configuration and consider batching requests when possible.
• The CLI/npx invocation assumes the civo-mcp package is available on npm; ensure you have internet access during first run.
• You can specify region and other parameters per command to filter results or target specific data centers.
• The Node.js requirement is Node 20 or newer; use a compatible runtime in your environment to avoid compatibility issues.
• If you hit authentication errors, verify that CIVO_API_KEY is correctly exported in your environment and that the key has sufficient permissions for the requested actions.