Skip to main content
Connect Cursor IDE to Control Plane to manage your infrastructure directly from your development environment.

Prerequisites

Cursor IDE

Download Cursor

Service Account Token

Create a service account with appropriate permissions

Configuration

1

Locate the Configuration File

The MCP configuration file location depends on your operating system:
OSConfiguration File Path
macOS~/.cursor/mcp.json
Windows%USERPROFILE%\.cursor\mcp.json
Linux~/.cursor/mcp.json
If the .cursor directory or mcp.json file doesn’t exist, create them.
2

Add the MCP Server Configuration

Open the mcp.json file and add the Control Plane MCP Server configuration using one of the methods below:
Use the mcp-remote bridge to connect via Node.js:
{
  "mcpServers": {
    "cpln": {
      "env": {
        "BEARER_TOKEN": "<your-service-account-token>"
      },
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.cpln.io/mcp",
        "--header",
        "Authorization: ${BEARER_TOKEN}"
      ]
    }
  }
}
Replace <your-service-account-token> with your actual service account token.
This method requires Node.js and npm to be installed on your system.
3

Reload Cursor

Reload the Cursor window (Cmd/Ctrl + Shift + P → “Developer: Reload Window”) for the configuration to take effect.
For the latest MCP configuration options, refer to the official Cursor MCP Documentation.

Verify the Connection

After configuration, verify the connection in Cursor’s AI chat:
List all cpln mcp server tools
The AI should list the available Control Plane MCP tools.

Example Usage

Here’s how to use Control Plane with Cursor’s AI:
1

Set Your Context

Use org "my-org" and gvc "my-gvc" for context.
2

Deploy a Workload

Create a publicly accessible workload called "my-api" using nginx:latest on port 80.
3

Get the Endpoint

Monitor the readiness of my-api and give me the public endpoint once it's ready.

Troubleshooting

  • Check that your service account token is valid
  • Ensure the token is entered without extra spaces or quotes
  • Verify the token has appropriate permissions (see Service Account Permissions)
  • Check for typos in the org name you’re using for context, this is a common cause of authentication failures

Next Steps