# Control Plane MCP server

> Deploy, troubleshoot and manage containerized workloads across AWS, GCP, Azure and other clouds on Control Plane.

- Listing: https://mcp.tc/i/control-plane
- Connect: use the server's own URL `https://mcp.cpln.io/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: Control Plane
- Homepage: <https://controlplane.com>
- Docs: <https://docs.controlplane.com/mcp/overview>
- Repository: <https://github.com/controlplane-com/ai-plugin>

## About

Connects an assistant to Control Plane, a platform that runs containerized workloads across AWS, GCP, Azure, OCI and private hardware under one API. The assistant can deploy workloads, troubleshoot restarts, set up domains with TLS, configure access to cloud resources, and migrate Kubernetes, Compose or Helm setups.

It runs as a hosted streamable HTTP endpoint at https://mcp.cpln.io/mcp. Sign-in uses OAuth 2.1 with PKCE, and you choose which Control Plane orgs the token may act on. The default URL serves the core tool set; adding ?toolsets=full exposes every tool. The tool list is not published, so specific tool names are unknown.

## What it can do

- Deploy and manage containerized workloads across multiple clouds
- Troubleshoot workloads that keep restarting
- Put a custom domain with auto-TLS in front of a workload
- Grant workloads credential-free access to cloud resources
- Provision stateful services such as Postgres with failover and backups
- Migrate Kubernetes, Compose or Helm configs to Control Plane

## Example prompts

- "Troubleshoot why my payments-api workload in production keeps restarting."
- "Put app.example.com in front of my web workload with auto-TLS."
- "Provision a production Postgres with HA failover and S3 backups."
- "Convert this kustomization.yaml to Control Plane and apply it to staging."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http control-plane https://mcp.cpln.io/mcp
```

2. Start Claude Code, type `/mcp`, pick **control-plane** and choose **Authenticate**. A browser window opens for the Control Plane sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Control Plane** and paste this URL:

```url
https://mcp.cpln.io/mcp
```

3. Click **Add**, then **Connect**, and sign in when Control Plane asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Control%20Plane&connectorUrl=https%3A%2F%2Fmcp.cpln.io%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.cpln.io/mcp` and click **Add**.

3. Click **Connect** and sign in when Control Plane asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.cpln.io/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Control Plane to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=control-plane&config=eyJ1cmwiOiJodHRwczovL21jcC5jcGxuLmlvL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "control-plane": {
      "url": "https://mcp.cpln.io/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=control-plane&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.cpln.io%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"control-plane","type":"http","url":"https://mcp.cpln.io/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "control-plane": {
      "type": "http",
      "url": "https://mcp.cpln.io/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "control-plane": {
      "serverUrl": "https://mcp.cpln.io/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add control-plane --url https://mcp.cpln.io/mcp
codex mcp login control-plane
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.control-plane]
url = "https://mcp.cpln.io/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http control-plane https://mcp.cpln.io/mcp
```

Then, inside Gemini CLI, run `/mcp auth control-plane` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "control-plane": {
      "type": "http",
      "url": "https://mcp.cpln.io/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.cpln.io/mcp`.

## Details

- Server version: 1.0.2
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-04
- Updated: 2026-10-04

---
Source: https://mcp.tc/i/control-plane (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
