codemagic-mcp is an MCP (Model Context Protocol) server designed to let AI agents operate Codemagic CI/CD as well as App Store Connect and Google Play through a unified interface, enabling a complete conversation-driven mobile app delivery pipeline—from connecting a repository, to building, signing, and releasing.
Purpose
The server provides AI agents with a toolset across five areas, covering the main stages of mobile app release:
- Codemagic: list teams and apps, trigger builds, wait for results, get build artifacts, pull build logs, manage variable groups, caches, and webhooks.
- App Store Connect: manage TestFlight, upload and submit builds, set listing copy and screenshots, validate, submit, and release to the App Store.
- Google Play: publish AABs, promote releases, manage staged rollouts, set listing copy and screenshots, read and reply to user reviews.
- Testing: parse JUnit XML test results from any Codemagic build, providing a summary of passed/failed/errored/skipped and detailed information for each failure.
- Cross-store: validate localized release notes according to each platform's character limits and BCP-47 language codes.
Main capabilities and expected flow
The end-to-end flow examples given in the material: 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
Usage
Environment requirements
- Node.js 20 or 22 (LTS)
- asc CLI (asccli.sh)—required for the App Store Connect tools
- google-play CLI (part of codemagic-cli-tools)—required for the Google Play tools, install command: pip install codemagic-cli-tools
Environment variables
Environment variables need to be set separately for the App Store Connect tools (iOS) and the Google Play tools (Android). Google Play credentials can use the @file: prefix to avoid pasting JSON inline.
Installation and running
Using npx is recommended, with no installation required; add the server to the MCP client configuration and it will be downloaded and run automatically. You can also install it permanently and use codemagic-mcp as the command, or build from source and use a local path. For development/testing, MCP Inspector can be used.
Connecting to Claude Desktop
Add the configuration to claude_desktop_config.json. Configuration file locations: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json After connecting, you can open a new conversation and ask "ping the codemagic mcp server" to verify; if connected, Claude will call the ping tool and reply "Codemagic MCP server is running." If not connected, check whether the args path is correct, whether the required environment variables are set, and fully restart Claude Desktop with Cmd+Q. If the server does not appear, check whether the CODEMAGIC_API_TOKEN environment variable is set correctly, and whether the path to dist/index.js is absolute and correct.
Workflow prompts
After connecting, entering / in the Claude Desktop input box opens the command selector, where you will see five workflow prompts from this server. After selecting a prompt, Claude receives a step-by-step playbook and begins usingAvailable tools to execute workflows.
Example conversations
Requirements can also be described in natural language, and Claude will automatically select the appropriate tools, for example:
- "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?"
Applicable scenarios
Suitable for developers or teams that need to manage iOS and Android app build, signing, and release processes conversationally through an AI agent, especially scenarios that use Codemagic CI/CD and involve both App Store Connect and Google Play.
Limitations and notes
- Inline YAML: trigger_build accepts an optional yaml_content parameter. When provided, the YAML is uploaded along with the build request and does not need to exist in the repository, making it suitable for agent-generated configuration.
- Build numbers: templates use $BUILD_NUMBER and $VERSION_NAME as ordinary variables, and no store queries are performed within the YAML. The agent needs to determine the correct values before triggering via list_asc_builds or list_google_play_tracks, then pass them in through the variables parameter of trigger_build.
- Signing: iOS signing is performed on the Codemagic build machine (macOS + keychain), and the MCP server does not directly handle signing identities.
- Teams and personal accounts: list_applications and list_builds accept an optional team_id. When not provided, operations target 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 not pass through the agent. After setup is complete, variable groups can be referenced by name through the groups parameter in trigger_build.
- Project structure: the src/ module contains pure functions (API calls, CLI wrappers) and does not depend on MCP; the src/tools/ module wires these functions into MCP tools and is responsible for input schemas, formatting, and error responses.
Other specific configuration details (such as the complete list of environment variables, credential fields for each platform, and the specific names and contents of the five workflow prompts) are not yet fully expanded in the provided materials.
