Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.controlplane.com/llms.txt

Use this file to discover all available pages before exploring further.

Connect Gemini CLI to Control Plane to manage your infrastructure through natural language conversations.

​
Prerequisites

Gemini CLI

Get started with Gemini CLI

Service Account Token

Create a service account with appropriate permissions

​
Configuration

​
Step 1: Add the MCP Server

Use the gemini mcp add command to register the Control Plane MCP Server: 
gemini mcp add --transport http cpln https://mcp.cpln.io/mcp \
  --header "Authorization: Bearer <your-service-account-token>" \
  --scope user
Replace <your-service-account-token> with your actual service account token.
We recommend the user scope to make the MCP server available across all your projects. Without --scope user, the default is local scope which only applies to the current directory.
You can also use --scope project to add the server for the current project only. See the Gemini CLI Documentation for more details on scopes.

​
Step 2: Verify the Connection

List your configured MCP servers to confirm the setup: 
gemini mcp list
You should see cpln listed with a successful connection: 
cpln: https://mcp.cpln.io/mcp (HTTP) - ✓ Connected

​
Managing MCP Servers

# List all MCP servers
gemini mcp list

# Remove an MCP server
gemini mcp remove cpln

# Get help on MCP commands
gemini mcp --help
For the latest configuration options and troubleshooting, refer to the official Gemini CLI Documentation.

​
Example Conversation

Here’s an example of deploying a public workload through Claude:
1

Set 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

Usage Examples

See practical examples of Control Plane operations

Policy Reference

Learn about permissions and access control