Codemagicmcp MCP Server

A local Python MCP server that exposes the [Codemagic CI/CD REST API](https://docs.codemagic.io/rest-api/overview/) as Claude-callable tools. Trigger

Local serverstdioPython

What is the Codemagicmcp MCP server?

Most cloud and infrastructure work still happens through a UI a human drives. Codemagicmcp MCP server moves it into the conversation instead. A 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.

The tools it exposes

The server publishes 5 tools. What each one is for:

  • Apps — The Apps tool exposed by this server
  • Builds — The Builds tool exposed by this server
  • Artifacts — The Artifacts tool exposed by this server
  • Caches — The Caches tool exposed by this server
  • Webhooks — The Webhooks tool exposed by this server

What it needs from you

Configuration is passed through the environment: CODEMAGIC_API_KEY, CODEMAGIC_DEFAULT_APP_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

The server ships on PyPI as codemagic-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Codemagicmcp's toolset — Apps, Builds, Artifacts and 2 more — is a fair guide to whether it matches your workflow. It is maintained by agimaulana; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
AppsThe Apps tool exposed by this server.
BuildsThe Builds tool exposed by this server.
ArtifactsThe Artifacts tool exposed by this server.
CachesThe Caches tool exposed by this server.
WebhooksThe Webhooks tool exposed by this server.

How to install the Codemagicmcp MCP server

{
  "mcpServers": {
    "codemagicmcp": {
      "command": "uvx",
      "args": ["codemagic-mcp"],
      "env": {
        "CODEMAGIC_API_KEY": "your-value",
        "CODEMAGIC_DEFAULT_APP_ID": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CODEMAGIC_API_KEYCredential the server authenticates with.Yes
CODEMAGIC_DEFAULT_APP_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Codemagicmcp to Apps.
  • Use Codemagicmcp to Builds.
  • Use Codemagicmcp to Artifacts.

Frequently asked questions

It connects Codemagicmcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Apps, Builds, Artifacts, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Codemagicmcp directly.