codemagic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEMAGIC_MODE | No | Permission mode. `read-only`: GET operations only; `builds`: also start/cancel builds, delete caches, create artifact links; `all`: every implemented mutation. | builds |
| CODEMAGIC_TOOLSET | No | Toolset exposure. `core` exposes 12–19 everyday tools; `all` exposes 64–106 tools. | core |
| CODEMAGIC_API_TOKEN | No | Personal Codemagic API token. Needed for API calls. Without it, the server runs in setup mode exposing only cm_setup_status. Can be supplied via environment or saved via `configure`. | |
| CODEMAGIC_CONFIG_DIR | No | Absolute directory holding credentials.env. | ~/.config/codemagic-mcp |
| CODEMAGIC_TIMEOUT_MS | No | Request timeout in milliseconds. Integer from 100 to 120000. | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cm_setup_statusA | Reports that this server has no Codemagic API token yet and returns the local steps to configure one. No API tools are exposed until a token is saved and the server is reconnected. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| capabilities | Enabled operations and API coverage. |
TDQS
Scored across 1 tool
With only a single tool exposed, there is no possibility of confusion or misselection between tools. The lone tool's purpose (reporting setup status) is unambiguous.
The single name 'cm_setup_status' uses a clean snake_case convention with a consistent 'cm_' namespace prefix. No pattern can be fully verified from one tool, but nothing is inconsistent or unreadable.
A Codemagic CI/CD integration would be expected to expose many build, app, and workflow operations, but only a single placeholder/setup tool exists. This is far too few for the apparent scope.
The server exposes no actual Codemagic API functionality; it only reports that no token is configured. The entire operational surface is missing, leaving agents with nothing to work with.