Control Plane
Operate multi-cloud workloads, secrets, and networking from your agent through Control Plane’s hosted MCP.
Overview
io.cpln/control-plane is a MCP server for the Operate phase that lets your agent deploy workloads and manage secrets and networking on Control Plane across AWS, GCP, Azure, and private clouds.
What is this MCP server?
- Streamable-http remote MCP at https://mcp.cpln.io/mcp (version 1.0.0)
- Deploy and operate workloads across AWS, GCP, Azure, and private clouds from one surface
- Secrets and networking operations exposed for agent-driven runbooks
- Backed by controlplane.com platform—not a single-repo shell script
- Suited to indie teams standardizing on Control Plane instead of bespoke Terraform per cloud
- Remote URL: https://mcp.cpln.io/mcp (streamable-http)
- MCP server version: 1.0.0
- Supports AWS, GCP, Azure, and private clouds per server description
What problem does it solve?
You juggle multiple cloud consoles and bespoke scripts whenever you ship fixes, rotate secrets, or tune networking.
Who is it for?
Solo builders and tiny teams already on Control Plane who want agent-assisted deploys and infra changes with a single control plane.
Skip if: Hackathon prototypes on a single static host with no Control Plane tenant or multi-cloud need.
What do I get? / Deliverables
After registration, your agent can drive Control Plane operations through one streamable-http MCP instead of context-switching across provider dashboards.
- Live MCP connection to Control Plane control plane API
- Agent-invoked deploy and operate actions on configured clouds
- Centralized secrets and networking changes without per-cloud CLI memorization
Recommended MCP Servers
Journey fit
Production ownership—deployments, secrets rotation, and cross-cloud networking—is the Operate shelf even when you first touch it during Ship. Infra is the canonical home for control-plane APIs that manage where and how workloads run, not frontend polish or landing copy.
How it compares
Multi-cloud control-plane MCP, not a local Docker-only dev skill or generic shell deploy script.
Common Questions / FAQ
Who is io.cpln/control-plane for?
Developers using Control Plane who ship to AWS, GCP, Azure, or private cloud and want MCP-driven operations from Claude Code, Cursor, or similar agents.
When should I use io.cpln/control-plane?
Use it during Operate and Ship when you deploy releases, manage secrets, or adjust networking—and want the agent to call Control Plane instead of manual console work.
How do I add io.cpln/control-plane to my agent?
Configure https://mcp.cpln.io/mcp as a streamable-http remote MCP server in your client and authenticate per Control Plane’s MCP onboarding for your organization.