Skip to main content
This page lists every tool the MCP Server exposes, grouped by the resource it operates on. You don’t call these tools yourself: describe the outcome you want (see Usage Examples) and the assistant picks the tools. Knowing what exists helps you prompt precisely and follow what the assistant does on your behalf.

Toolset profiles

The server advertises a different set of tools depending on the toolsets query parameter on the endpoint URL. A smaller set keeps the assistant focused and fits comfortably in its context window; the larger sets unlock specialized resource families.
Connecting to https://mcp.cpln.io/mcp with no query parameter gives you the core profile. To switch profiles, point your client at the URL with the ?toolsets= parameter — see your tool’s setup page for where the endpoint URL is configured.

Reading the tables

Each tool is listed with its name, its label, and what it does. The Access column flags how the tool behaves: Tools available only in a larger profile are marked mk8s or full next to the access marker; everything else is in core. The readonly profile has every Read tool except plan_app, browse_templates, create_agent, and how_to_create_cloud_account.

Docs & guidance

Tools the assistant uses to ground itself in accurate Control Plane facts and documentation. The two documentation tools, search_control_plane and query_docs_filesystem_control_plane, are proxied from the standalone docs MCP at docs.controlplane.com/mcp; the rest are served by the MCP Server itself.

Generic resource tools

The single read and delete tools that work for every resource kind. Use these to list, inspect, or delete resources: pass the kind (workload, secret, gvc, and so on). All are in core.

Jobs

Each job tool does a whole task in one call: it reads the state it needs, makes the change, and returns the outcome. deploy_app, add_database, restart_workload, rollback_workload, promote_workload, and grant_cloud_access then wait up to 40 seconds by default for the result; when the task needs longer, the result names the exact call that continues it. All are in core except promote_workload, which is in full.

GVCs

Create and manage GVCs and the cloud locations they span.

Workloads

Create, update, run, and operate workloads. Deploying, restarting, rolling back, promoting, and diagnosing a workload each take one call with the job tools. The advanced configure_workload_* tools each manage one specialized block of the spec and live in the full profile.

Images

Build container images on Control Plane and follow the build. An image record is created by pushing, so there is no create or update tool — list, inspect, and delete image records with the generic tools using kind: image. No Docker daemon is involved: the build service clones the repository or assembles the stored app files, detects how to build it (using the Dockerfile when one is present, otherwise by auto-detecting the stack), and always produces a linux/amd64 image. deploy_app under Jobs builds and deploys in one call.
The MCP server has no access to your filesystem, so a folder on your machine builds through the CLI instead: cpln image build --remote --dir PATH --name NAME:TAG uploads the folder and builds it the same way, also without Docker.
A private repository needs a one-time browser authorization per organization. The first build that needs it returns an authorization link instead of starting a build; open the link, approve access, then ask the assistant to build again. The link is single-use and expires in about 15 minutes. Later builds in that organization run without prompting.

Secrets

Secret values never pass through the chat. list_resources and get_resource show a secret’s metadata, never its data. create_secret fills a new secret with values Control Plane generates, or hands you a Console link where you type values only you have; rotate_secret replaces the values and restarts the workloads that use them. No tool accepts or reveals a secret value. delete_resource under Generic resource tools deletes a secret. To let a workload read a secret, use grant_workload_secret_access under Workloads; deploy_app and promote_workload grant it for the secrets their env references.

Custom domains

Configure custom domains, their port listeners, routes, TLS, and CORS. update_domain changes all of them on an existing domain.

Identity & access

Manage identities, policies, groups, service accounts, and the private-network resources attached to an identity. Creating and updating identities and policies works in core; the rest are in full. For one workload, credential-free cloud access takes one call with grant_cloud_access under Jobs, and secret access with grant_workload_secret_access under Workloads.

Template catalog

Browse and operate the Template Catalog: production-ready stacks you install instead of hand-authoring resources. For PostgreSQL, MySQL, MariaDB, MongoDB, or Redis, add_database under Jobs installs the template with generated credentials in one call; install_template takes them only for a setting add_database does not take, such as backups.

Volume sets & storage

Create volume sets, mount them to workloads, and manage their volumes and snapshots. Per-volume operations and snapshot changes go through run_volumeset_command, and get_resource lists a volume set’s snapshots. Creating a volume set on its own is in full; mount_volumeset_to_workload creates a missing one.

Observability

Inspect deployments, logs, events, replicas, metrics, traces, the audit trail, and the status of asynchronous operation commands. All are in core except the event, replica, and command lists, which are in full.

Terraform & IaC

Convert manifests to Terraform and export existing resources as HCL for infrastructure as code.
Terraform and Pulumi tag every resource they manage with cpln/managedByTerraform: "true". When get_resource reads such a resource, or a tool updates one, the result tells the assistant to warn you: a change made through the MCP server drifts from your code, and the next apply can revert it unless your code gets the change too.

Cloud accounts, agents & networking

Onboard cloud accounts, create agents for private connectivity, and reserve IP sets. All are in full.

Organization & operations

Find the orgs a connection can use, and manage org settings, quotas, audit contexts, and external logging. All are in full except list_orgs and request_quota_increase.

Managed Kubernetes

Provision and update managed Kubernetes clusters on every supported provider with two tools that take the provider and its settings. They are available in the mk8s and full profiles: connect to https://mcp.cpln.io/mcp?toolsets=mk8s to use them.

Next steps

MCP Server

Endpoint, authentication, and the compatible-tools list

Usage Examples

Practical prompts that put these tools to work

AI Plugin

Skills, agents, commands, and guardrails on top of the MCP server

Reference

The full configuration and behavior of every Control Plane resource