CodemagicMcp
Let your agent trigger Codemagic CI/CD builds, inspect artifacts, and manage caches while you ship mobile or multi-platform apps.
Overview
Codemagic MCP is an MCP server for the Ship phase that lets your agent manage Codemagic CI/CD builds, apps, artifacts, and caches via the Codemagic API.
What is this MCP server?
- PyPI package CodemagicMcp (version 0.6.2) with stdio transport
- Manage Codemagic builds, apps, artifacts, and build caches from the agent
- CODEMAGIC_API_KEY required (User Settings → Integrations → Codemagic API)
- Optional CODEMAGIC_DEFAULT_APP_ID and CODEMAGIC_BASE_URL (default https://api.codemagic.io)
- Package version 0.6.2 on PyPI identifier CodemagicMcp
- Required env: CODEMAGIC_API_KEY
- Default API base: https://api.codemagic.io (overridable)
Community signal: 1 GitHub stars.
What problem does it solve?
You lose flow jumping between chat and Codemagic’s UI every time you need a rebuild, artifact link, or cache clear during a release push.
Who is it for?
Solo mobile or cross-platform builders already on Codemagic who use Claude Code or Cursor during release week.
Skip if: Teams on GitHub Actions-only workflows with no Codemagic account, or builders who only need local test runs without cloud CI.
What do I get? / Deliverables
After configuring the API key and stdio server, your agent can drive Codemagic operations so you stay in one thread while shipping.
- Agent-driven Codemagic build and cache operations
- Access to build artifacts and app management without leaving the agent UI
Recommended MCP Servers
Journey fit
Codemagic is used when binaries are ready to build, sign, and release—canonical placement is Ship where launch automation and release pipelines live for solo mobile teams. Launch under Ship captures CI/CD release actions (builds, artifacts, caches) distinct from local unit testing or pre-merge code review.
How it compares
Codemagic CI/CD control plane MCP, not an App Store metadata or Huawei gallery upload server.
Common Questions / FAQ
Who is Codemagic MCP for?
Developers using Codemagic CI/CD who want their coding agent to manage builds, apps, artifacts, and caches through MCP.
When should I use Codemagic MCP?
Use it in Ship when you are launching builds, chasing release artifacts, or maintaining Codemagic caches during mobile or multi-platform delivery.
How do I add Codemagic MCP to my agent?
Install the CodemagicMcp PyPI package, set CODEMAGIC_API_KEY (and optional CODEMAGIC_DEFAULT_APP_ID), register stdio MCP in your client, then call Codemagic tools from the agent.