Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Civo (BYOK) — connector documentation

  • MCP endpoint: https://byok-civo.connectorbay.com/mcp
  • REST API: POST https://byok-civo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-civo.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Civo API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-civo.connectorbay.com/health · Tool schemas: https://byok-civo.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-civo · agent@connectorbay.com

What Civo (BYOK) is for

Civo (BYOK) lets an AI assistant read your own Civo data through the Civo API with a key you supply (API key). Read-only: 8 tools (list_regions, list_sizes, list_instances, get_instance, list_volumes, get_quota, list_dns_domains, list_charges). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.civo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Civo. Civo and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Civo regions are available?"
  • "What instance sizes does Civo offer?"
  • "What Civo instances do I have running?"
  • "Show details of this Civo instance"
  • "What Civo volumes do I have?"
  • "How much of my Civo quota am I using?"

What it does

  • list_regions: List the Civo regions with code, name, country, default flag, capacity flag and supported features.
  • list_sizes: List the Civo instance sizes with CPU cores, RAM, disk and whether each can be selected.
  • list_instances: List the Civo compute instances in a region with size, status, IP addresses, tags and resources. Initial passwords, SSH keys and scripts are not returned.
  • get_instance: Get one Civo instance by id: size, status, IP addresses, tags and resources. Initial passwords and SSH keys are not returned.
  • list_volumes: List the Civo block storage volumes in a region with size, status and the instance each is attached to.
  • get_quota: Show the Civo account quota limits and current usage: instances, CPU, RAM, disk, volumes, snapshots, IPs, networks and firewalls.
  • list_dns_domains: List the DNS domain names managed in the Civo account with id and name.
  • list_charges: List Civo chargeable resources with code, label, period, hours billed and region. A date range of at most 31 days; defaults to the current month so far.

BYOK key

You bring your own Civo API key (https://dashboard.civo.com/security). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.civo.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Civo API (api.civo.com) with a BYOK key; documentation: https://www.civo.com/api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Civo. Civo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Civo account.

Built for: Worldwide. Languages: English.