Control Plane
Multi-cloud workloads, GVCs, infrastructure
About Control Plane
Control Plane is a platform for running cloud-native workloads across multiple clouds and regions from a single control plane. Its remote MCP server lets assistants inspect and manage workloads, GVCs, and related infrastructure resources in a Control Plane organization directly from conversation.
Connection details
https://mcp.cpln.io/mcp- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add control-plane --transport http https://mcp.cpln.io/mcpFrequently asked questions
What is the Control Plane remote MCP server?
The Control Plane remote MCP server is a hosted Model Context Protocol endpoint at https://mcp.cpln.io/mcp, so AI assistants can connect to it without installing or running anything locally. Control Plane is a platform for running cloud-native workloads across multiple clouds and regions from a single control plane. Its remote MCP server lets assistants inspect and manage workloads, GVCs, and related infrastructure resources in a Control Plane organization directly from conversation.
How do I connect to the Control Plane MCP server?
Add the endpoint https://mcp.cpln.io/mcp to any MCP-compatible client such as Claude Code, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
Does the Control Plane MCP server require authentication?
Yes. Control Plane uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.
Which transport does the Control Plane MCP server use?
Control Plane exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
More remote MCP servers
