mcp-codemagic
Allows triggering and inspecting mobile/Flutter builds via the Codemagic REST API, including listing apps, starting builds, checking build status, listing builds, and canceling builds.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-codemagic List my Codemagic apps and their workflows."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-codemagic
An MCP server for Codemagic CI/CD. Trigger and inspect mobile/Flutter builds straight from Claude Code (or any MCP client) using the Codemagic REST API.
Built and maintained by MusicTech Lab.
Features
Tool | Description |
| List all applications and their workflow ids |
| Get one application's repo, branches, and workflows |
| Trigger a build for an app/workflow on a branch or tag |
| Get the status and details of a build |
| List builds, filterable by app/workflow/branch/status |
| Cancel a running or queued build |
Related MCP server: Codemagic
Requirements
Python 3.10+
A Codemagic API token
Setup
git clone https://github.com/musictechlab/mcp-codemagic.git
cd mcp-codemagic
poetry install
cp .env.example .env # then fill in CODEMAGIC_API_KEYGetting your API token
In Codemagic, go to User settings → Integrations → Codemagic API (or Team settings → Integrations for team accounts) and copy the token. Put it in .env:
CODEMAGIC_API_KEY=your-codemagic-api-tokenRunning
poetry run python -m mcp_codemagic
# or, via the installed console script:
poetry run mcp-codemagicConnecting to Claude Code
Add the server with the CLI:
claude mcp add codemagic -- poetry --directory /absolute/path/to/mcp-codemagic run python -m mcp_codemagicOr add it manually to your MCP config:
{
"mcpServers": {
"codemagic": {
"command": "poetry",
"args": ["--directory", "/absolute/path/to/mcp-codemagic", "run", "python", "-m", "mcp_codemagic"],
"env": { "CODEMAGIC_API_KEY": "your-codemagic-api-token" }
}
}
}Example prompts
"List my Codemagic apps and their workflows."
"Start the
ios-releaseworkflow for app<app-id>onmain.""What's the status of build
<build-id>?""Show the last builds for app
<app-id>that are still building.""Cancel build
<build-id>."
Examples
List apps
"List my Codemagic apps and their workflows."
Calls codemagic_list_apps and returns each application with its id and workflow ids:
{
"applications": [
{
"_id": "6a28af80c12e620808693f7b",
"appName": "vimoswim-coach",
"repository": { "htmlUrl": "https://github.com/vimoswim/vimoswim-coach" },
"workflowIds": ["6a28af80c12e620808693f7a"]
}
]
}Trigger a build
"Start workflow
6a28af80c12e620808693f7afor app6a28af80c12e620808693f7bonmain."
Calls codemagic_start_build and returns the new build id:
{ "buildId": "6a28f92cf7acee31a7394057" }Check build status
"What's the status of build
6a28f92cf7acee31a7394057?"
Calls codemagic_get_build. The status field moves through queued → building → finishing → publishing → finished:

{
"build": {
"_id": "6a28f92cf7acee31a7394057",
"status": "queued",
"branch": "main",
"workflowId": "6a28af80c12e620808693f7a",
"instanceType": "mac_mini_m2"
}
}Errors come back as JSON (never raised), so the agent can read them:
{ "error": "Codemagic API 404 for GET /builds/missing", "status": 404, "body": { "message": "Build not found" } }Configuration
Variable | Required | Default | Description |
| yes | — | Codemagic API token ( |
| no |
| Override the API base URL |
Development
poetry install
poetry run ruff check .
poetry run ruff format --check .
poetry run pytestContributing
See CONTRIBUTING.md.
Security
To report a vulnerability, see SECURITY.md.
License
MIT — see LICENSE.
Available Tools
6 toolscodemagic_cancel_buildA
Cancel a running or queued build.
Args: build_id: The id of the build to cancel.
Inputs: build_id (required). Returns: result
codemagic_get_appA
Get details for a single Codemagic application.
Returns the app's repository, branches, workflows, and recent build references.
Args: app_id: The Codemagic application id (from codemagic_list_apps).
Inputs: app_id (required). Returns: result
codemagic_get_buildA
Get the status and details of a single build.
Status values include "queued", "building", "finishing", "publishing", "finished" (with a success/failed result), "canceled", and "timeout".
Args: build_id: The build id returned by codemagic_start_build or listed by codemagic_list_builds.
Inputs: build_id (required). Returns: result
codemagic_list_appsA
List all applications connected to your Codemagic account.
Returns each application's id, name, connected repository, and the workflow ids defined in its codemagic.yaml. Use the app id and a workflow id with codemagic_start_build to trigger a build.
Inputs: no named parameters. Returns: result
codemagic_list_buildsA
List builds, optionally filtered by app, workflow, branch, or status.
Args: app_id: Only builds for this application id. workflow_id: Only builds for this workflow id. branch: Only builds for this branch. status: Only builds with this status (e.g. "building", "finished").
Inputs: app_id, workflow_id, branch, status. Returns: result
codemagic_start_buildA
Trigger a new build for an app/workflow on a branch or tag.
Provide exactly one of branch or tag. Returns the new buildId, which you can poll with codemagic_get_build.
Args: app_id: The Codemagic application id. workflow_id: The workflow id from codemagic.yaml (e.g. "ios-release"). branch: Branch to build (e.g. "main"). Mutually exclusive with tag. tag: Git tag to build (e.g. "v1.2.0"). Mutually exclusive with branch.
Inputs: app_id (required), workflow_id (required), branch, tag. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a unique, clearly defined purpose: listing apps, getting app details, listing builds, getting build details, starting a build, and canceling a build. There is no overlap or ambiguity between them.
All tools follow a consistent 'codemagic_verb_noun' pattern using snake_case (e.g., codemagic_list_apps, codemagic_start_build). This makes the tool set predictable and easy to navigate.
With 6 tools, the set is well-scoped for a CI/CD server. It covers essential operations without being overwhelming or too sparse.
Core build lifecycle (list, start, get, cancel) is covered. Minor gaps exist, such as no explicit tool for retrying a build or downloading artifacts, but the set is functional for typical workflows.
Maintenance
Related MCP Connectors
MCP server for Appcircle mobile CI/CD platform.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Trigger and inspect Codemagic CI builds, apps and artifacts.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Related MCP Servers
- AlicenseBqualityCmaintenanceA server that enables interaction with Jenkins CI/CD pipelines from any compatible MCP client (like Claude Desktop), allowing users to manage jobs, builds, coverage reports, and other Jenkins functionality through natural language.11500 npmMIT
- AlicenseAqualityCmaintenanceA local Python MCP server that exposes the Codemagic CI/CD REST API as Claude-callable tools. Trigger builds, manage apps, download artifacts, and clear caches — all from Claude Code or Claude Desktop without leaving the chat.252MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Codemagic CI/CD API, enabling app management, build operations, artifact handling, cache control, and team management through natural language.12 npm3MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that provides seamless access to Codemagic CI/CD APIs, enabling natural language interaction with applications, builds, artifacts, caches, and teams.1616MIT