Toolset profiles
The server advertises a different set of tools depending on thetoolsets 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.
Docs & guidance
Read-only tools the assistant uses to ground itself in accurate Control Plane facts, schemas, and documentation before acting. All are incore.
Generic resource tools
The single read and delete tools that work for every resource kind. Use these to list, inspect, or delete resources — pass thekind (workload, secret, gvc, and so on); secrets are read-only. All are in core.
GVCs
Create and manage GVCs and the cloud locations they span.Workloads
Create, update, run, and operate workloads. The advancedconfigure_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 usingkind: image.
No Docker daemon is involved: the build service clones the repository, detects how to build it (using the Dockerfile when one is present), and always produces a
linux/amd64 image. Building an existing NAME:TAG replaces that image, so prefer a fresh tag.
Only repository builds run through the MCP server — it has no access to your filesystem. To build a local folder, run
cpln image build --remote, which uploads the folder and builds it the same way, also without Docker.Secrets
Secrets are read-only through the MCP server:list_resources and get_resource show that a secret exists and its metadata — never its data. No tool creates, edits, deletes, or reveals a secret; secret data and lifecycle are managed by you in the Console, the CLI, Terraform, Pulumi, or the API. To let a workload consume an existing secret, use grant_workload_secret_access under Workloads.
Custom domains
Configure custom domains, their port listeners, routes, TLS, and CORS. Port, route, TLS, and CORS tools operate on an existing domain.Identity & access
Manage identities, policies, groups, service accounts, and the private-network resources attached to an identity. Groups, service accounts, network resources, and user invitations are infull.
Template catalog
Browse and operate the Template Catalog — production-ready stacks you install instead of hand-authoring resources.Volume sets & storage
Create volume sets, mount them to workloads, and manage their volumes and snapshots. Snapshot and per-volume operations are infull.
Observability
Inspect deployments, logs, events, replicas, metrics, traces, the audit trail, and the status of asynchronous operation commands. All are incore.
Terraform & IaC
Convert manifests to Terraform and export existing resources as HCL for infrastructure as code. Batch export and kind discovery are infull.
Cloud accounts, agents & networking
Onboard cloud accounts, create agents for private connectivity, and reserve IP sets. All are infull.
Organization & operations
Manage org settings, quotas, audit contexts, and external logging. All are infull except list_quotas.
Managed Kubernetes
Provision and update managed Kubernetes clusters across cloud and bare-metal providers. This family is available in themk8s and full profiles — connect to https://mcp.cpln.io/mcp?toolsets=mk8s to use it.
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