codemagic-mcp

An MCP (Model Context Protocol) server that gives AI agents a unified surface over Codemagic CI/CD and App Store Connect / Google Play, enabling a complete mobile app delivery pipeline — from onboarding a repository through building, signing, and publishing — driven by conversation.

What it does

The server exposes tools across five domains:

• Codemagic — list teams and apps, trigger builds, wait for results, retrieve artifacts, fetch build logs, manage variable groups, caches, and webhooks
• App Store Connect — manage TestFlight, upload and submit builds, set listing text and screenshots, validate, submit, and release to the App Store
• Google Play — publish AABs, promote releases, manage staged rollouts, set listing text and screenshots, read and reply to user reviews
• Testing — parse JUnit XML test results from any Codemagic build; get a pass/fail/error/skip summary with per-failure details
• Cross-store — validate localized release notes against platform char limits and BCP-47 locale codes

The intended end-to-end flows are:

iOS: list_asc_builds → get_yaml_template → trigger_build → wait_for_build → upload_build_to_asc → set_version_metadata → validate_app_submission → submit_for_app_store_review → release_version

Android: get_latest_build_number → get_yaml_template → trigger_build → wait_for_build → upload_to_google_play → promote_google_play_release

Prerequisites

• Node.js 20 or 22 (LTS)
• asc CLI — asccli.sh — required for App Store Connect tools
• google-play CLI — part of codemagic-cli-tools — required for Google Play tools
  Terminal

  Copy

  pip install codemagic-cli-tools
  

Environment variables

Required

App Store Connect tools (iOS)

Google Play tools (Android)

For the Google Play credentials you can use the @file: prefix to avoid pasting JSON inline:

GOOGLE_PLAY_SERVICE_ACCOUNT_CREDENTIALS=@file:/path/to/service-account.json

Installation

Using npx (recommended)

No installation needed. Add the server to your MCP client config with npx and it downloads and runs automatically:

"command": "npx",
"args": ["-y", "codemagic-mcp-server"]

See the Claude Desktop section below for the full config.

Global install

If you prefer a permanent install instead of npx:

npm install -g codemagic-mcp-server

Then use codemagic-mcp as the command in your MCP client config:

"command": "codemagic-mcp",
"args": []

Development

To build from source:

git clone https://github.com/todah-zg/codemagic-mcp.git
cd codemagic-mcp
npm install
npm run build

Then use the local path in your MCP config — see Running from a local clone below.

Running

MCP Inspector (development / testing)

Set the required environment variables in your shell, then:

npx @modelcontextprotocol/inspector node dist/index.js

Claude Desktop

Add to your claude_desktop_config.json:

If installed from npm

{
  "mcpServers": {
    "codemagic": {
      "command": "npx",
      "args": ["-y", "codemagic-mcp-server"],
      "env": {
        "CODEMAGIC_API_TOKEN": "your-token",
        "ASC_KEY_ID": "your-key-id",
        "ASC_ISSUER_ID": "your-issuer-id",
        "ASC_PRIVATE_KEY_B64": "base64-encoded-p8-key",
        "ASC_BYPASS_KEYCHAIN": "1",
        "GOOGLE_PLAY_SERVICE_ACCOUNT_CREDENTIALS": "@file:/path/to/service-account.json"
      }
    }
  }
}

If running from a local clone (development):

{
  "mcpServers": {
    "codemagic": {
      "command": "node",
      "args": ["/absolute/path/to/codemagic-mcp-server/dist/index.js"],
      "env": {
        "CODEMAGIC_API_TOKEN": "your-token",
        "ASC_KEY_ID": "your-key-id",
        "ASC_ISSUER_ID": "your-issuer-id",
        "ASC_PRIVATE_KEY_B64": "base64-encoded-p8-key",
        "ASC_BYPASS_KEYCHAIN": "1",
        "GOOGLE_PLAY_SERVICE_ACCOUNT_CREDENTIALS": "@file:/path/to/service-account.json"
      }
    }
  }
}

The config file is at:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Using with Claude Desktop

Connecting the server

To verify the server is connected, open a new conversation and ask: "ping the codemagic mcp server". If connected, Claude will call the ping tool and respond with "Codemagic MCP server is running." If not connected, check that the path in args is correct and that all required environment variables are set, then restart Claude Desktop with Cmd+Q (not just closing the window).

If the server does not appear, check that the CODEMAGIC_API_TOKEN environment variable is set correctly in the config and that the path to dist/index.js is absolute and correct.

Workflow prompts

Once connected, type / in the Claude Desktop input field to open the command picker. You will see five workflow prompts from this server:

Select a prompt and Claude will receive a step-by-step playbook and begin executing the workflow using the available tools.

Example conversations

You can also describe what you want in plain language — Claude will select the right tools automatically:

"I have a Flutter app at github.com/example/myapp. Set it up on Codemagic and get a first build running."

"Trigger a release build for my Android app, version 2.1.0. The last build number on Google Play was 41."

"What is the current App Store review status for my iOS app?"

Config file location

Tools

Codemagic

App Store Connect (iOS)

Google Play (Android)

Testing

Cross-store

Variable Groups

YAML

Prompts

Prompts are reusable workflow playbooks. In Claude Desktop they appear as slash commands. An agent can also invoke them by name to get step-by-step instructions for a complete workflow.

Project structure

src/
  index.ts              — Server setup, env validation, transport
  codemagic.ts          — Codemagic API functions (v3 + v1)
  asc.ts                — App Store Connect CLI wrapper
  googleplay.ts         — Google Play CLI wrapper
  androidpublisher.ts   — Google Play androidpublisher REST API client (listings, screenshots, reviews)
  testing.ts            — JUnit XML parser (no external dependencies)
  ssh.ts                — SSH key generation and deploy key setup
  yaml.ts               — YAML validation logic
  templates.ts          — Static codemagic.yaml templates
  detection.ts          — Project type detection from repository file listings
  prompts.ts            — MCP prompt resources (workflow playbooks)
  tools/
    codemagic.ts        — Codemagic MCP tool registrations
    asc.ts              — App Store Connect MCP tool registrations
    googleplay.ts       — Google Play MCP tool registrations
    yaml.ts             — YAML MCP tool registrations
    releasenotes.ts     — Release notes validation tool
    readiness.ts        — Publish readiness check tool
    testing.ts          — Test results tool

The src/ modules contain pure functions (API calls, CLI wrappers) with no MCP dependency. The src/tools/ modules wire those functions up as MCP tools — input schemas, formatting, error responses.

Notes

• Inline YAML: trigger_build accepts an optional yaml_content parameter. When provided, the YAML is uploaded alongside the build request and does not need to exist in the repository. Useful for agent-generated configurations.
• Build numbers: Templates use $BUILD_NUMBER and $VERSION_NAME as plain variables — no store lookups happen inside the YAML. The agent determines the correct values via list_asc_builds or list_google_play_tracks before triggering, then passes them through the variables parameter of trigger_build.
• Signing: iOS signing happens on the Codemagic build machine (macOS + keychain). The MCP server never handles signing identities directly.
• Team vs. personal account: list_applications and list_builds accept an optional team_id. Without it, they operate on the authenticated user's personal account.
• Variable groups and secrets: add_variable only creates non-secret variables. Secret values (API keys, certificates, tokens) should be added directly in the Codemagic UI — secrets should never pass through the agent. Once set up, reference groups by name in trigger_build via the groups parameter.