Cycle.io Brings Natural Language Infrastructure Management to Vultr with New MCP Server

Cycle.io has launched a new Model Context Protocol (MCP) server, now available to use with Vultr. The new capability enables developers and platform teams to connect MCP-compatible AI assistants and coding tools to Cycle.io and interact with their applications and infrastructure using natural language.

For teams using Cycle.io with Vultr, this means they can ask questions, troubleshoot issues, and perform approved actions without constantly switching between their IDE, infrastructure dashboards, monitoring tools, logs, and APIs.

From AI assistant to infrastructure operations

Cycle.io provides a unified control plane for deploying and managing applications and infrastructure. Through its integration with Vultr, teams can provision and manage Vultr infrastructure directly from Cycle.io.

The new MCP server adds a natural-language interface to that experience. Developers can ask questions such as:

• Is anything down in production right now?
• What changed before this service started failing?
• Show me the latest CPU and memory telemetry.
• Search the logs for this environment.
• Where are my servers and workloads currently running?

Cycle.io can then surface relevant information about applications and infrastructure, including events, metrics, logs, networking, DNS, load balancer traffic, and workload health.

This can be especially useful when troubleshooting. Instead of manually checking multiple systems to find the source of a problem, developers can use their AI assistant to investigate the issue and identify potential causes.

Moving from answers to actions

Cycle.io's MCP server goes beyond retrieving information. With the appropriate permissions, developers can also use an AI assistant to perform supported actions through Cycle.io.

These include deploying applications, starting or restarting containers and environments, updating configurations, managing DNS and ingress, and moving workloads between servers, data centers, or cloud providers.

For example, a developer could describe a multi-container application and ask their assistant to create an environment and deploy it, without having to translate that request into individual API calls and configurations manually.

These actions are governed by Cycle's existing capability system and API key permissions. Teams can define what an MCP-connected assistant can access and what it is allowed to change.

At launch, Cycle.io's MCP server includes 18 tools: 10 read-only tools, 7 mutation tools, and 1 command execution tool, with additional capabilities in development.

Using Cycle.io MCP with Vultr

Cycle.io's integration with Vultr enables teams to provision and manage Vultr cloud infrastructure through Cycle's control plane. The new MCP server gives those teams another way to interact with their applications and infrastructure through the AI assistants and development tools they already use.

For platform teams, this can also simplify developer self-service. Developers can set up and access approved infrastructure and operational capabilities through an MCP-compatible assistant, while platform teams retain control over the permissions and actions available to them.

The result is a simpler path from asking a question to understanding what is happening to taking an approved action, without requiring developers to move between multiple operational tools.

Meet Vultr at AgentCon and MCPCon Amsterdam

Have questions about Cycle.io's new MCP capabilities and how to use them with Vultr? Get in touch with the Vultr team.

If you're attending AgentCon and MCPCon Amsterdam on September 17, meet the Vultr team and talk to us about Cycle.io, MCP, and how AI-assisted infrastructure operations can work on Vultr.