Civo MCP server

What the model can do

Civo cloud: regions, instances with size, status, IPs and tags, one instance's load, Kubernetes clusters with node pools and versions, volumes, DNS domains and records, hours of use per resource, and account quota against its limits; when you ask, can reboot, stop, start, retag, resize, create or delete an instance, add or delete a DNS domain, add, change or delete a DNS record, recycle a Kubernetes node, delete a Kubernetes cluster or a volume.

Reads

• civo_regionsCivo regions this account can use: code (LON1, NYC1 …), name, country, whether it is the default, whether it is out of capacity…
• civo_instancesInstances (virtual machines) in a region: hostname, size, status, public and private IP, CPU, RAM, disk, tags and network.
• civo_instanceOne instance by id with its current CPU, memory and storage use (Civo's stats line) as well as size, status, IPs and tags.
• civo_kubernetes_clustersKubernetes clusters in a region: name, status, ready, node count and size, node pools, Kubernetes version and any upgrade available…
• civo_volumesBlock storage volumes in a region: name, size in GB, status, and the instance or cluster it is attached to (or none).
• civo_dnsCivo DNS: without domain_id, the domains in the account; with domain_id, that domain's records (type, name, value, TTL, priority)…
• civo_chargesHours of use per chargeable resource (instances, volumes, clusters …) for a period of at most 31 days: product code, label, region, from…
• civo_quotaThe account's quota: limit and current use for instances, CPU cores, RAM, disk, volumes, snapshots, public IPs, networks, firewalls and ports.

Acts, when you ask

These change something in Civo. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• civo_reboot_instanceReboots a Civo instance now.
• civo_stop_instanceShuts a Civo instance down.
• civo_start_instanceStarts a stopped Civo instance.
• civo_set_instance_tagsReplaces ALL of a Civo instance's tags with the list given (tags not in the list are removed; an empty list clears them).
• civo_resize_instanceResizes a Civo instance upwards to another size (e.g. g3.medium), within the account's quota.
• civo_create_instanceCreates (builds) a new Civo instance in the region given, which starts hourly billing at the size's price straight away.
• civo_delete_instancePermanently deletes a Civo instance and its disk.
• civo_create_dns_domainAdds a domain name to Civo DNS so records can be created for it.
• civo_delete_dns_domainPermanently removes a domain from Civo DNS together with ALL its records, immediately and with no confirmation step…
• civo_create_dns_recordAdds a DNS record to a Civo DNS domain; it is live as soon as caches expire (TTL at least 600 seconds).
• civo_update_dns_recordChanges a Civo DNS record (type, name, value, priority or TTL); only the fields passed change, and the change is live as soon as caches expire.
• civo_delete_dns_recordPermanently deletes a DNS record from a Civo DNS domain, immediately; whatever it pointed to stops resolving under that name.
• civo_recycle_kubernetes_nodeDeletes and rebuilds one node of a Civo Kubernetes cluster (for a node that is misbehaving)…
• civo_delete_kubernetes_clusterPermanently deletes a Civo Kubernetes cluster and all its nodes and workloads.
• civo_delete_volumePermanently deletes a Civo volume and the data on it, freeing the space (and its cost).

Connect it

First connect Civo on Dashboard → Connections, then add Memtro to your client once. The Civo tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Civo connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which Civo instances are running in LON1?
• › How much CPU quota headroom do we have left?
• › Is a Kubernetes upgrade available for our production cluster?
• › What DNS records does acme.com have in Civo?
• › How many hours did our instances run this month?

Questions

Is this an official Civo MCP server?

No. It is Memtro's MCP server with Memtro's Civo connector behind it: the connector reads Civo through its API with the credentials you connect on Dashboard → Connections, and Civo publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Civo?

Only when you ask, and only what it has been granted: reboot an instance (hard or soft); stop an instance; start a stopped instance; replace an instance's tags; resize an instance to a larger size; create an instance (starts hourly billing); delete an instance; add a DNS domain; delete a DNS domain and all its records; add a DNS record; change a DNS record; delete a DNS record; recycle (rebuild) a Kubernetes node; delete a Kubernetes cluster; delete a volume. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server