Codemagic MCP

What todah-zg/codemagic-mcp MCP server does

The todah-zg/codemagic-mcp MCP server exposes mobile delivery operations through the Model Context Protocol. It connects an authenticated Codemagic account with App Store Connect and Google Play workflows, covering tasks from repository onboarding to build execution and store publishing.

On the Codemagic side, agents can discover teams, applications, workflows, and builds; start, monitor, or cancel builds; retrieve build details and step logs; and work with caches and webhook subscriptions. The server can also connect a Git repository to Codemagic and generate a time-limited public URL for a build artifact.

Its iOS tools cover App Store Connect app and TestFlight build discovery, beta groups and testers, external beta review, export compliance, version metadata, submission validation, and IPA uploads. The project description also identifies Android publishing through Google Play as part of the supported mobile delivery pipeline.

How it works

MCP-compatible clients call the server’s tools as needed. A typical Codemagic flow starts by finding an application and its workflows, then triggering a build and checking its state with wait_for_build. That tool returns immediately, so an agent calls it again until the build reaches a terminal state. Build details, artifacts, and per-step logs can then be inspected.

For iOS delivery, an agent can find a TestFlight build, upload an IPA, update localized release metadata, declare export compliance, and run a preflight validation before submission. TestFlight groups and testers can be managed through separate tools. The server also provides a ping operation for checking whether the process is available.

Setup and configuration

The todah-zg/codemagic-mcp MCP server requires Node.js 20 or 22. The documented no-install launch command uses the npm package codemagic-mcp-server through npx:

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

CODEMAGIC_API_TOKEN is required for the Codemagic account. App Store Connect operations use ASC_KEY_ID, ASC_ISSUER_ID, and ASC_PRIVATE_KEY_B64; ASC_BYPASS_KEYCHAIN=1 can force authentication through environment variables instead of the macOS keychain. Google Play operations use GOOGLE_PLAY_SERVICE_ACCOUNT_CREDENTIALS, which may contain raw JSON or an @file: reference.

The README documents Claude Desktop configuration on macOS and Windows. It also describes building from a local clone with npm install, npm run build, and Node.js, but local paths must be supplied in the client configuration.

Tools and capabilities

Supported operations include:

• Listing teams, applications, workflows, builds, App Store Connect apps, TestFlight builds, and beta groups.
• Triggering, waiting for, inspecting, logging, and cancelling Codemagic builds.
• Adding repositories and managing webhooks and build caches.
• Uploading IPAs, adding TestFlight testers, creating groups, and submitting beta reviews.
• Setting export compliance and version metadata, then validating an App Store submission.
• Creating temporary public artifact download URLs.

Limitations and notes

The server does not replace the external credentials or accounts required by Codemagic, App Store Connect, or Google Play. Store-specific environment variables are only needed for the corresponding operations. wait_for_build performs one status check per call rather than holding an open wait, so clients must repeat it while a build is running. The provided setup documentation specifically describes Claude Desktop; compatibility with other MCP clients is not established by the supplied material.