Civo MCP. Manage K8s, instances, and networks with chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Civo (Cloud-native Kubernetes Cloud Provider API) lets you manage your entire cloud infrastructure right through your AI client. Provision K3s clusters, launch and resize compute instances, configure private networks, and monitor usage—all using plain English commands.
What your AI agents can do
Add team member
Adds a specific user to an existing team within Civo.
Attach volume
Connects a stored volume of data to a running compute instance.
Create cluster
Builds and provisions an entirely new Kubernetes cluster environment (K3s).
Create, list, and recycle nodes in K3s clusters across multiple regions using specific cluster management tools.
Launch new virtual machines, reboot them, resize their CPU/RAM, or stop them entirely with direct commands.
Build private networks and enforce security boundaries by creating specific firewall rules and network segments.
Create new block storage volumes, attach them to running instances, or detach them when they're done.
Get real-time reports on resource limits, usage quotas, and detailed hourly charges for your cloud account.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Civo (Cloud-native Kubernetes Cloud Provider API) MCP Server: 33 Tools
This collection of tools allows you to perform every major infrastructure task—from creating clusters and managing VMs to configuring networks and checking billing quotas—all through your AI client.
019e5d07add team member
Adds a specific user to an existing team within Civo.
019e5d07attach volume
Connects a stored volume of data to a running compute instance.
019e5d07create cluster
Builds and provisions an entirely new Kubernetes cluster environment (K3s).
019e5d07create domain
Registers a new DNS domain name with Civo.
019e5d07create domain record
Adds a specific record (like an A or CNAME) to your managed DNS zone.
019e5d07create firewall
Establishes a new, isolated firewall boundary for network traffic control.
019e5d07create firewall rule
Adds a specific rule (e.g., allow port 80) to an existing firewall.
019e5d07create instance
Launches a new virtual machine instance with specified size and region.
019e5d07create network
Builds a brand new private network segment for your cloud resources.
019e5d07create team
Creates an organizational team group within the Civo account.
019e5d07create volume
Allocates a new block storage volume that can be used later.
019e5d07create webhook
Sets up an endpoint to notify external services when events happen in Civo.
019e5d07detach volume
Removes a stored volume from an instance, making it available for reuse.
019e5d07get charges
Retrieves a detailed report of hourly charges for resources you've used this billing cycle.
019e5d07get quota
Checks your current resource limits and how much of those quotas you've consumed.
019e5d07list clusters
Lists all Kubernetes clusters currently active in your account.
019e5d07list disk images
Shows you the available templates or operating system images to use when creating instances.
019e5d07list domains
Lists all DNS domains managed within your Civo account.
019e5d07list firewall rules
Retrieves a list of all existing security rules attached to a firewall.
019e5d07list networks
Lists every private network segment you've set up in your account.
019e5d07list regions
Provides a list of all geographical regions where you can deploy resources.
019e5d07list sizes
Shows the available CPU/RAM sizes for compute instances (e.g., g3.xsmall).
019e5d07list ssh keys
Retrieves a list of SSH keys uploaded to your Civo account.
019e5d07reboot instance
Performs an immediate hard reboot on a specific compute instance.
019e5d07recycle cluster node
Restarts a single node within a Kubernetes cluster to refresh its state.
019e5d07resize instance
Increases or decreases the CPU and RAM size of an existing instance.
019e5d07retag instance
Applies new descriptive tags to a compute instance for organization.
019e5d07soft reboot instance
Performs a graceful operating system reboot on the running instance.
019e5d07start instance
Powers on an existing, stopped compute instance.
019e5d07stop instance
Shuts down a running compute instance to save costs.
019e5d07test webhook
Sends a test payload to verify that your configured webhook endpoint is active and receiving data.
019e5d07update team member status
Changes the status (active/inactive) of a user within an organizational team.
019e5d07upload ssh key
Securely adds a new SSH public key to your account for access control.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Civo (Cloud-native Kubernetes Cloud Provider API), then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You've got full control over your whole cloud setup with this server. It lets your AI client manage everything in Civo—from provisioning entire Kubernetes clusters to tweaking network firewalls—all using plain English commands, no dashboard clicking required.
Provisioning and Managing Compute Instances
You can launch a new virtual machine instance by calling create_instance, specifying the size and region. If you need more juice later on, use resize_instance to adjust the CPU or RAM. You'll also need to know what's available; check out list_sizes for current compute specs and list_disk_images to see templates.
Need a quick restart? Use soft_reboot_instance for a graceful OS reboot, or hit reboot_instance if you gotta hard reboot it immediately. You can power up an instance that's been shut down using start_instance, and remember to run stop_instance when you don't need it to save cash. For organization, tag your machines with retag_instance.
If you’re done with a machine but want to keep the credentials handy, upload new access keys via upload_ssh_key, or see what keys are already there by running list_ssh_keys.
Kubernetes Cluster Control
Managing K3s clusters is straightforward. You can build and provision an entirely new Kubernetes cluster environment using create_cluster. If you need to check the status of your setups, run list_clusters. To refresh a node's state without taking the whole cluster down, use recycle_cluster_node, and if you’re only listing what exists, list_clusters gets everything.
Networking and Security Configuration
Building out your network infrastructure is simple. First, create a brand new private network segment with create_network. When you need to lock down traffic, establish an isolated boundary using create_firewall, then use create_firewall_rule to add specific rules—like allowing port 80—or check existing security settings with list_firewall_rules. For domain names and DNS records, you can register a new zone with create_domain or list existing domains using list_domains.
You then pinpoint the exact record using create_domain_record, and if you're just checking what you own, list_domains does the trick. Finally, when your setup changes, set up an automated alert endpoint by running create_webhook, and test that connection with test_webhook.
Storage and Data Management
Don't sweat storage. You can allocate a new block volume using create_volume, or check what volumes are already waiting for you with the system’s list functions. When an instance needs data, connect a stored volume using attach_volume; when it's time to clean house, use detach_volume.
Billing and Resource Oversight
Knowing what you spend is key. You can get a detailed report of all hourly charges for the current billing cycle by calling get_charges. Want to know your limits? Use get_quota to check resource consumption against set quotas. For a full picture, run list_regions to see where you can deploy resources, and list_networks shows every private network segment you’ve established.
Team and User Management
Managing who has access is just as important. You can create new organizational groups with create_team, then add specific users to that team using add_team_member. If someone's status needs updating, change it with update_team_member_status.
How Civo MCP Works
- 1 1. Subscribe to the server and provide your Civo API Key.
- 2 2. Tell your AI client what you need (e.g., 'I need a new web server in US-East').
- 3 3. The agent runs the necessary tools (
create_instance,create_network, etc.) automatically, confirming each step for you.
The bottom line is: You talk to your AI client like talking to a teammate and get infrastructure changes done without copy-pasting API calls.
Who Is Civo MCP For?
This is for the Ops Engineer who gets tired of clicking through four different dashboards just to provision one test environment. It's for the developer who needs to spin up a staging cluster right from their IDE chat window, and the SRE who has to check billing quotas before scaling up.
Automates complex infrastructure setups, like creating a new network segment followed by provisioning multiple K3s clusters in sequence.
Monitors resource usage and budget limits using get_quota and manages security by updating firewall rules (create_firewall_rule).
Quickly spins up temporary, isolated development environments or testing instances directly from the chat interface.
What Changes When You Connect
- It lets you build a full stack environment in one go. Need to test microservices? Run
create_networkfirst, then launchcreate_instance, and finally useattach_volume. It handles the dependency chain for you. - Billing stops being a guessing game. Use
get_quotato see your resource limits before launching anything big, and runget_chargesafterward to get an accurate hourly usage report. - You don't have to SSH in just to reboot something. Use
reboot_instanceorsoft_reboot_instancedirectly through a simple chat command. It’s fast. - Scaling is straightforward. Instead of manually editing config files, you can use
resize_instanceto immediately upgrade an instance's power when traffic spikes. - Security setup gets faster. Need to open port 443 for a new service? Run
create_firewall_ruleand specify the source/destination instantly.
Real-World Use Cases
Spinning up Dev Testbeds
A developer needs an isolated testing area. They tell their agent: 'Set up a new private network in eu-west, create one instance of size g3.small, and attach the volume named dev-data.' The agent executes create_network, then create_instance, followed by attach_volume—all without human intervention.
Scaling a Production Service
The SRE notices CPU usage spiking. They ask the agent to check the quota (get_quota), see they have capacity, and immediately command: 'Resize the production web server instance by 20%.' The agent runs resize_instance instantly.
Debugging Network Issues
A service fails to connect. Instead of checking logs everywhere, the engineer asks the agent to list all relevant firewall rules (list_firewall_rules) and check if a specific port is open for the new instance.
Full Environment Tear-Down
The project is finished. The team needs to delete resources safely. They ask the agent to list all existing clusters (list_clusters), confirm the nodes, and then initiate cleanup protocols for compute and networking.
The Tradeoffs
Trying to reboot an instance manually.
Logging into the dashboard, clicking 'Actions' > 'Reboot', waiting 30 seconds, then checking if it worked. It’s slow and requires context switching.
→
Just tell your agent: 'Hard reboot the web server.' The agent runs reboot_instance directly via API call. Done.
Forgetting to check billing limits.
Launching three new large clusters because they thought they had unlimited budget, only to hit a quota limit and face unexpected charges.
→
Always run get_quota before scaling. This confirms your resource ceiling and usage against the allocated budget.
Assuming network connectivity is automatic.
Creating an instance and expecting it to talk to other services without manually defining IP ranges or rules, leading to 'Connection Refused' errors.
→
First, define the boundary using create_network. Then, use create_firewall and create_firewall_rule before deploying any compute resources.
When It Fits, When It Doesn't
Use this if your workflow requires combining multiple, distinct infrastructure actions into a single conversational step. If you are constantly moving between 'I need to check the network' -> 'Now I need to make an instance' -> 'Wait, do I have storage?'—this is for you. It handles multi-step dependency calls.
Don't use this if all you need is a single action (e.g., just running list_domains). For simple checks or isolated tasks, those tools work fine. But if the process requires sequence and state management (like creating a network before creating an instance in that network), this MCP Server is necessary.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Civo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 33 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Managing cloud infrastructure shouldn't feel like clicking through five different tabs.
Today, provisioning a simple test environment means jumping between the Compute dashboard to launch the VM, then hitting the Networking tab to create an IP range, and finally going into Storage to attach a volume. You copy IDs from one screen and paste them into another. It’s tedious.
With this MCP server, you just tell your agent: 'Build me a testbed with two instances in network X, attached to volume Y.' The whole sequence—network creation, instance launch, storage attachment—runs automatically behind the scenes. You get immediate confirmation of the resources deployed.
The Civo MCP Server: Run complex resource provisioning from chat.
Manual setup requires you to check `list_regions` for availability, then run `create_network`, wait for the ID, and only then can you pass that ID into `create_instance`. The failure point is always human error in sequencing or copying IDs.
Now, your agent manages that entire sequence. You ask it to build a resilient cluster; it figures out the optimal order: Network -> Cluster -> Instances. It handles the complexity so you don't have to.
Common Questions About Civo MCP
How do I check if my current cloud usage is over budget using get_quota? +
Yes, running get_quota shows your resource limits and how much of them you've used. It’s the first step before scaling anything up or out.
Can I create a cluster and assign it to a specific network using create_cluster? +
Yes, by providing the necessary network IDs and parameters in your prompt. The agent uses create_network and related tools to ensure the new K3s cluster is isolated correctly.
What's the difference between reboot_instance and soft_reboot_instance? +
A soft reboot runs the OS shutdown command, letting services close cleanly. A hard reboot forces an immediate power cycle (reboot_instance), which is faster if you suspect a hung service.
I need to connect a volume, do I use attach_volume or create_volume? +
You must always create_volume first to allocate the storage space. Then, run attach_volume, specifying the new volume ID and the target instance's ID.
How do I find out what regions are available for deployment? +
Run list_regions. This tool gives you a list of all geographical locations where Civo supports deploying compute resources and networks.
When I run `upload_ssh_key`, how does the system ensure my private key remains secure? +
The public component is uploaded and associated with your account. Your AI client only sends the required fingerprint data, ensuring that the sensitive private key never leaves your local machine.
After I use `create_network`, what must I do to restrict inbound traffic using `create_firewall`? +
You need to follow up immediately with create_firewall and then define specific rules. Remember that new networks default to denying all incoming connections, so you have to explicitly allow ports.
If I need to take an instance offline for maintenance, should I use `stop_instance` or delete it? +
Use stop_instance. This action suspends the compute resource while retaining its disk state and configuration. Deleting the instance removes all associated data permanently.
Can I create a Kubernetes cluster in a specific region? +
Yes, you can use the create_cluster tool and specify the region parameter (e.g., 'lon1' or 'nyc1') along with the cluster name and network ID.
How do I restart a stuck compute instance? +
You can use the reboot_instance tool for a hard reboot or soft_reboot_instance for a graceful restart by providing the Instance ID.
Can I check my current cloud spending and limits? +
Absolutely. Use the get_charges tool to see your current billing details and get_quota to check your account resource limits.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
HackerOne
Automate bug bounty management via HackerOne — manage reports, programs, and payments directly from any AI agent.
Blockdaemon (Blockchain Infrastructure)
Access institutional-grade blockchain data across multiple protocols — list blocks, track transactions, and retrieve financial reports via Blockdaemon Ubiquity.
DataFrame Aggregator Engine
Perform blazingly fast GroupBy and Aggregations on massive CSVs local. Save millions of AI tokens and get mathematically perfect sums, means, and counts.
You might also like
Document Paginator Engine
Mathematically slice massive text blocks into token-safe chunks without ever truncating critical sentences.
Douyu
Automate game broadcasting metrics via the Douyu API — monitor live streamer activity, track esports massive bullet-chats, and extract audience retention natively from any AI agent.
Lingyi Wanwu
Orchestrate Lingyi Wanwu AI models — manage chat completions, embeddings, and monitor Yi model performance directly from any AI agent.