Civo MCP by usefulapi
List Civo instances, Kubernetes clusters, networks and DNS; reboot instances, add rules
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.Similar tools
Listed for the same task: automate CI/CD pipelinesReviews
No review yet. Used Civo MCP by usefulapi? Be the first to help others choose.What it does
Civo MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://civo.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http civo https://civo.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"civo": {
"url": "https://civo.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Civo MCP by usefulapi answered an MCP connection on 15 Nov 2026 and introduced itself as civo-mcp 1.39.2 (MCP protocol 2025-06-18).
22 tools offered to AI assistants
civo_list_regions· List the Civo regions available to the account, with which one is the default, whether each is out of capacity, and the features each supports (IaaS, Kubernetes, object store, load balancers, GPU, databases). A cheap way to confirm the APIcivo_get_quota· The account's limits and current usage: instances, CPU cores, RAM, disk, volumes, snapshots, public IPs, networks, firewalls and rules, load balancers, object storage and databases. Answers 'can I launch another one?'. Civo: GET /v2/quota.civo_list_charges· List billable usage for a period: each resource's product code, label, region, time span and hours (size_gb for volumes). The range may be at most 31 days; defaults to the start of the current month until now. Civo: GET /v2/charges.civo_list_instance_sizes· List the sizes (plans) that can be launched — instances, Kubernetes nodes and databases — with CPU cores, RAM, disk, transfer allowance and GPU. Civo: GET /v2/sizes.civo_list_instances· List compute instances in a region, optionally filtered by tags. Paginated: returns {page, per_page, pages, items}. Passwords are redacted. Civo: GET /v2/instances.civo_get_instance· Fetch one instance: status, size, CPU/RAM/disk, public and private IPs, network, firewall, tags, attached volumes and source image. Passwords are redacted. Civo: GET /v2/instances/{id}.civo_list_kubernetes_clusters· List the Kubernetes (K3s/Talos) clusters in a region with status, version, node pools, API endpoint and installed applications. Paginated: {page, per_page, pages, items}. Kubeconfigs are redacted. Civo: GET /v2/kubernetes/clusters.civo_get_kubernetes_cluster· Fetch one Kubernetes cluster: status, readiness, conditions, version and available upgrade, pools and their instances, network, firewall, CNI and installed marketplace apps. The kubeconfig is redacted. Civo: GET /v2/kubernetes/clusters/{id}civo_list_networks· List the private networks in a region: label, CIDR, whether it is the default network, status and nameservers. Civo: GET /v2/networks.civo_list_firewalls· List the firewalls in a region with their network, rule count and how many instances, clusters and load balancers use each. Civo: GET /v2/firewalls.civo_list_firewall_rules· List the rules of one firewall: protocol, port range, CIDRs, direction (ingress/egress), action (allow/deny) and label — the answer to 'what is exposed to the internet?'. Civo: GET /v2/firewalls/{id}/rules.civo_list_load_balancers· List the load balancers in a region: algorithm, backends (IP, protocol, source/target ports), public IP, state and the Kubernetes service each fronts. Civo: GET /v2/loadbalancers.
Show 10 more
civo_list_volumes· List the block-storage volumes in a region: size, status, type, and the instance or cluster each is attached to (unattached volumes still bill). Civo: GET /v2/volumes.civo_list_databases· List the managed databases (MySQL, PostgreSQL) in a region: software and version, size, nodes, IPs, port, network, firewall and status. Paginated: {page, per_page, pages, items}. Passwords are redacted. Civo: GET /v2/databases.civo_list_dns_domains· List the domains whose DNS Civo hosts for the account. Civo: GET /v2/dns.civo_list_dns_records· List the records of one hosted domain (name, type, value, priority, TTL), optionally filtered by type or name. Civo: GET /v2/dns/{domain_id}/records.civo_reboot_instance· Reboot one instance. `soft` (default) asks the OS to restart cleanly; `hard` cuts power and boots it again, like pulling the plug — use only when soft does not work. Causes brief downtime. Civo: POST /v2/instances/{id}/soft_reboots or /hardcivo_stop_instance· Power off one instance. Anything it serves goes offline until it is started again with civo_start_instance. A stopped instance is still billed. Civo: PUT /v2/instances/{id}/stop.civo_start_instance· Boot a stopped instance. Undoes civo_stop_instance. Civo: PUT /v2/instances/{id}/start.civo_set_instance_tags· REPLACE the full tag list of one instance (tags are used for filtering and by load-balancer instance pools, so changing them can move an instance in or out of a pool). Pass the complete desired list; an empty list clears all tags. Civo: PUTcivo_create_firewall_rule· Add one rule to a firewall — e.g. allow TCP 443 ingress from 0.0.0.0/0. This changes what is reachable on every instance, cluster and load balancer using the firewall, so prefer narrow CIDRs. Undo by deleting the rule in the Civo dashboardcivo_create_dns_record· Add one record to a Civo-hosted domain. Live DNS changes propagate to the world; undo by deleting the record in the Civo dashboard or CLI. Civo: POST /v2/dns/{domain_id}/records.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.40.0 | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Hosted endpoint | https://civo.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Website | https://usefulapi.io/civo/ | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 9h ago |
Change history
- VERSION16 Nov 20261.39.3 → 1.40.0
- VERSION16 Nov 20261.39.2 → 1.39.3
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.0 → 1.39.0
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.5 → 1.37.0
- VERSION07 Nov 20261.36.4 → 1.36.5
- VERSION07 Nov 20261.36.3 → 1.36.4
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Civo MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Civo MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Civo MCP by usefulapi
How do I connect Civo MCP by usefulapi?
Use the hosted endpoint https://civo.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Civo MCP by usefulapi offer?
When Electra Index connected on 15 Nov 2026, it listed 22 tools: civo_list_regions, civo_get_quota, civo_list_charges, civo_list_instance_sizes, civo_list_instances, civo_get_instance, civo_list_kubernetes_clusters, civo_get_kubernetes_cluster and more. The full list is in "Live check" above.
Is Civo MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use Civo MCP by usefulapi for?
Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.