Skip to main content
This page provides practical examples of how to interact with Control Plane through AI assistants using the MCP Server. These examples work across all compatible tools.

Setting Context

Before performing operations, always set your organization and GVC context:
Setting context once at the start of a conversation helps the AI assistant understand which resources to target.

GVC Operations

Create a GVC

Create a new Global Virtual Cloud with specific locations. You can use friendly location names or technical location IDs:
You can use friendly location names (like “Frankfurt”, “Virginia”, “Dublin”) or technical location IDs (like “aws-eu-central-1”, “aws-us-east-1”). The MCP server will resolve friendly names to the appropriate location IDs.

List GVCs

Get GVC Details


Workload Operations

Create a Workload

Create a new workload with various configurations:

Update a Workload

List Workloads

Get Workload Status

Delete a Workload

Deletion operations are irreversible. The AI assistant should be configured to confirm before executing destructive operations.

Image Operations

Build an Image

The assistant can build a container image straight from a GitHub or GitLab repository and push it to your org’s private registry. No Docker daemon and no CLI are involved — the build runs on Control Plane, and the assistant follows it until the image is pushed.
The first build from a private repository returns a one-time authorization link instead of starting: open it, approve access for your organization, then ask the assistant to build again. Later builds run without prompting.
To build a local folder, the assistant will hand you a cpln image build --remote command to run yourself — it has no access to your filesystem. That still needs no Docker daemon, only the CLI with a profile authenticated to the target organization. See build options.

Check a Build

List Images

Get Image Details


Secret Management

Wire an Existing Secret

Secret data is managed by you — in the Console, CLI, Terraform, Pulumi, or the API. The assistant verifies a secret exists and wires access to it; it never reads or writes secret values.
When granting workload access to secrets, describe the desired outcome — the MCP server will automatically create the identity, policy, and workload binding in one step.

Policy & Access Control

Manage Policies


Domain Configuration


Cloud Accounts


Suggestion Tools

Plan Before Executing


Workload Logs

Query Logs

The get_workload_logs tool builds LogQL queries automatically from structured parameters. Use the query parameter for advanced LogQL syntax.

Complex Workflows

Full Application Deployment

Environment Promotion

Debugging Session


Next Steps

Tool Setup

Configure MCP for your preferred tool

Workload Reference

Learn more about workload configuration options

GVC Concepts

Understand Global Virtual Clouds

Policy Reference

Configure permissions for your authorized orgs