MCP Server

Connect any MCP-compatible AI tool to Control Plane.

The Control Plane MCP Server lets any AI tool with Model Context Protocol support manage Control Plane resources through natural-language conversations.

If your AI tool supports plugins — Claude Code, Codex, or Antigravity CLI — start with the Control Plane AI Plugin instead. The plugin auto-configures this MCP server and adds skills, agents, commands, and guardrails on top.

Endpoint

url · string · required

https://mcp.cpln.io/mcp

Authentication

OAuth with per-org consent. Your AI tool walks you through it on first use — see your tool’s setup page below for the exact trigger.

Toolset profiles

The full tool catalog is larger than most AI tools can hold in context at once — and some clients cap how many tools they accept. So each connection selects a toolset profile with the toolsets query parameter. Pick one — core, mk8s, and full are nested (each is a superset of the one above), and readonly stands on its own:

Profile	What it includes
readonly	Investigation only. Metrics, logs, traces, workload events, replicas and deployments, quotas, the audit trail, configuration inventory, and Terraform export — plus a generic read tool that works on every resource kind. It advertises no tool that creates, updates, deletes or executes a command, so an assistant on this profile cannot change a live resource.
core (default)	The everyday deploy-and-operate journey: GVCs, workloads, deployments, logs, image builds, custom domains, identities, policies, the template catalog, volume sets, Terraform export, metrics, traces, and the audit trail — plus a generic read/delete tool that works on every resource kind, and a raw-API escape hatch for anything else.
mk8s	Everything in core, plus the typed BYOK managed-Kubernetes (mk8s) cluster tools (create/update across all 11 providers).
full	Everything in mk8s, plus the full administrative and fine-tuning surface: cloud-account registration (AWS/GCP/Azure/NATS), org IAM (users, groups, service accounts, policy edits), network-bridge agents, identity network-resource bindings, IP sets, audit contexts, advanced workload tuning (load balancer, sidecar, rollout, security, retry, external logging), deep custom-domain editing (routes, ports, CORS, TLS), volume-set snapshots / expand / shrink, and org/GVC settings.

Examples

https://mcp.cpln.io/mcp                    # core (default)
https://mcp.cpln.io/mcp?toolsets=readonly  # reads only, no writes
https://mcp.cpln.io/mcp?toolsets=mk8s      # core + BYOK Kubernetes
https://mcp.cpln.io/mcp?toolsets=full      # everything

An unknown value returns a 400 listing the accepted names (readonly, core, mk8s, full). So does combining readonly with another profile — it withholds the write tools the others add, so the two cannot be mixed.

Which profile should I use? full is the complete catalog — it’s what the AI Plugin configures for every client. Pick core (the default) for a lighter, focused catalog if your client caps tool counts or loads every tool definition up front; it still covers the whole build-and-operate workflow (it can read and delete any resource kind generically, and reaches anything else through the raw-API tool). Use mk8s when you manage BYOK Kubernetes clusters. Use readonly to point an assistant at production for performance work, incident triage, or an audit without the possibility of an unintended change.

The profile is fixed for the life of a connection — an AI agent can’t expand it mid-session. If your assistant says a Control Plane tool isn’t available, reconnect with the profile that includes it.

Compatible tools

Claude Code

Claude Code CLI

Claude Desktop

Claude apps for Mac & Windows

Claude Web

claude.ai in the browser

Codex

OpenAI Codex

Cursor

Cursor IDE

VS Code

Visual Studio Code

Antigravity

Google Antigravity (CLI or IDE)

Amp

Sourcegraph Amp

OpenCode

OpenCode terminal assistant

Don’t see your tool listed? Any client that supports remote MCP servers can connect — point it at https://mcp.cpln.io/mcp and let it handle OAuth.

Next steps

Tools Reference

Every tool the server exposes, grouped by resource, with toolset profiles

Usage Examples

Practical prompts for common Control Plane workflows

AI Plugin

Recommended path for Claude Code, Codex, Antigravity CLI

Access Control

Scope what an AI tool can do in your org with policies and least privilege