CodemagicMcp

io.github.AgiMaulanaPublished by GitHub account AgiMaulanav0.6.2Updated Oct 24, 2026

Codemagic CI/CD MCP Server — manage builds, apps, artifacts, and caches from your AI

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant manage Codemagic CI/CD builds, apps, artifacts, caches, variables, and webhooks through the Codemagic REST API.

What you can do
Exposes the Codemagic CI/CD REST API as assistant-callable tools. It can list and inspect apps and builds, trigger or cancel builds, read build and step logs, list artifacts, and create time-limited public artifact URLs. It also manages build caches, app environment variables, and webhooks, including delete operations marked destructive.
When to use it
Useful when a team builds and ships through Codemagic and wants to check build status, trigger or cancel builds, pull logs and artifacts, or adjust caches, variables, and webhooks from the chat instead of the Codemagic web UI.
Requirements
Runs locally as a Python package (Python 3.11+) via uvx, pip, or source, over stdio. Requires a Codemagic API key in CODEMAGIC_API_KEY; optional CODEMAGIC_BASE_URL and CODEMAGIC_DEFAULT_APP_ID. Needs network access to the Codemagic API. Desktop client only.
Before you install
The API key in CODEMAGIC_API_KEY grants access to the Codemagic account and is stored in the client config. Several tools are destructive and can delete apps, caches, environment variables, and webhooks, or cancel running builds; add_variable and update_variable write secrets into app configuration. create_artifact_public_url produces a time-limited public link to build artifacts. Step logs may be written to local temp files.

Installation

In SourceWeft

  1. Open CodemagicMcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Codemagic MCP Server

[MCP Registry]

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 Claude Desktop without leaving the chat.

[Codemagic MCP server]

[CodemagicMcp MCP server] [MCP Badge] [License: MIT]

Tools

Apps

ToolDescription
list_appsList all applications in your Codemagic account
get_appGet details of a specific application
add_appAdd a public repository to Codemagic
add_private_appAdd a private repository using an SSH key
delete_app ⚠️Delete an application from Codemagic

Builds

ToolDescription
list_buildsList builds, optionally filtered by app
get_buildGet build details with step count summary; pass include_steps=True for full step list
trigger_buildTrigger a new build for an application
cancel_build ⚠️Cancel a running build
get_build_logsGet a step-by-step status summary of a build (filterable by status)
get_step_logsGet raw logs inline or create/update a managed temp file for a specific build step
get_step_log_artifactCheck whether a managed local step-log artifact still exists for a specific build step
list_build_artifactsList all artifacts produced by a build

Artifacts

ToolDescription
get_artifact_urlGet the download URL for a build artifact
create_artifact_public_urlCreate a time-limited public URL for an artifact

Caches

ToolDescription
list_cachesList all build caches for an application
delete_cache ⚠️Delete a specific build cache
delete_all_caches ⚠️Delete all build caches for an application

Environment Variables

ToolDescription
list_variablesList all environment variables for an application
add_variableAdd an environment variable to an application
update_variableUpdate an existing environment variable
delete_variable ⚠️Delete an environment variable

Webhooks

ToolDescription
list_webhooksList all webhooks for an application
add_webhookAdd a webhook to an application
delete_webhook ⚠️Delete a webhook

⚠️ These tools are marked as destructive and will prompt for confirmation before executing.

Quick Start

The fastest way to get running with Claude Code — no separate install step needed:

bash
# 1. Add the server (uses uvx to run it on-demand)claude mcp add codemagic -e CODEMAGIC_API_KEY=your-api-key-here -- uvx codemagic-mcp
# 2. Restart Claude Code — tools will appear in /tools

That's it. See Configuration for optional settings like CODEMAGIC_DEFAULT_APP_ID.


Installation

Requirements: Python 3.11+

Option 1 — uvx (recommended, no install needed)

bash
uvx codemagic-mcp

Option 2 — pip

bash
pip install codemagic-mcp

Option 3 — from source

bash
git clone https://github.com/AgiMaulana/CodemagicMcp.gitcd CodemagicMcppython3 -m venv .venv.venv/bin/pip install -e .

Configuration

Get your API token from Codemagic User Settings → Integrations → Codemagic API.

You can provide settings as environment variables or via a .env file:

bash
# .envCODEMAGIC_API_KEY=your-api-key-here
# Optional: set a default app so you don't have to specify it every timeCODEMAGIC_DEFAULT_APP_ID=your-app-id-here
# Optional: customize managed temp log storage for get_step_logs(..., delivery="file")CODEMAGIC_LOG_TEMP_DIR=/tmp/codemagic-mcpCODEMAGIC_LOG_TTL_SECONDS=3600CODEMAGIC_LOG_CLEANUP_INTERVAL_SECONDS=300CODEMAGIC_LOG_MAX_TOTAL_BYTES=524288000CODEMAGIC_LOG_MAX_FILE_COUNT=200

Default App ID

CODEMAGIC_DEFAULT_APP_ID is optional but recommended if you work primarily with one app. When set, the AI will use it automatically whenever a tool requires an app_id and none was specified. If it is not set, the AI will:

  1. Call list_apps to discover available apps.
  2. Use the app automatically if only one exists.
  3. Present the list and ask you to choose if multiple apps are found.

Step Log File Delivery

get_step_logs supports two delivery modes:

  • delivery="file" is the default and writes the log to a managed local temp file, returning metadata such as artifact_id, file_path, bytes, line_count, and expires_at.
  • delivery="inline" returns the raw step log text directly.

The local file mode is useful when a step log is too large to comfortably return inline. Managed log files are stored under CODEMAGIC_LOG_TEMP_DIR and expired files are cleaned up opportunistically whenever a new log file is written. The default retention window is controlled by CODEMAGIC_LOG_TTL_SECONDS and defaults to 3600 seconds.

The server also runs a startup cleanup pass and a periodic background cleanup loop. The loop interval is controlled by CODEMAGIC_LOG_CLEANUP_INTERVAL_SECONDS and defaults to 300 seconds. As an additional safety backstop, the managed temp directory is capped by CODEMAGIC_LOG_MAX_TOTAL_BYTES and CODEMAGIC_LOG_MAX_FILE_COUNT; when either cap is exceeded, the oldest files are evicted first.

get_step_log_artifact(build_id, step_id) checks whether that managed artifact still exists without calling Codemagic again or returning the file contents. The artifact metadata includes a deterministic artifact_id in this format:

text
artifact_<build_id>_<step_id>

If the artifact is missing, the server returns status="missing" with reason not_generated_or_expired, which means the file was either never generated or it expired and was deleted.

Register with Claude Code

Run the following command to add the server:

bash
claude mcp add codemagic -- codemagic-mcp

Then set your API key in the MCP env config, or export it in your shell before starting Claude Code:

bash
export CODEMAGIC_API_KEY=your-api-key-here

Alternatively, add it manually to ~/.claude.json:

json
{  "mcpServers": {    "codemagic": {      "command": "codemagic-mcp",      "env": {        "CODEMAGIC_API_KEY": "your-api-key-here",        "CODEMAGIC_DEFAULT_APP_ID": "your-app-id-here"      }    }  }}

Using uvx (no prior installation needed)

json
{  "mcpServers": {    "codemagic": {      "command": "uvx",      "args": ["codemagic-mcp"],      "env": {        "CODEMAGIC_API_KEY": "your-api-key-here",        "CODEMAGIC_DEFAULT_APP_ID": "your-app-id-here"      }    }  }}

Restart Claude Code — the tools will appear in /tools.

Register with Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "codemagic": {      "command": "codemagic-mcp",      "env": {        "CODEMAGIC_API_KEY": "your-api-key-here",        "CODEMAGIC_DEFAULT_APP_ID": "your-app-id-here"      }    }  }}

Restart Claude Desktop to pick up the changes.

Project Structure

codemagic_mcp/├── config.py        # pydantic-settings config (validates API key at startup)├── client.py        # httpx async client, one method per endpoint├── server.py        # FastMCP instance└── tools/    ├── apps.py    ├── builds.py    ├── artifacts.py    ├── caches.py    ├── variables.py    └── webhooks.py

Adding New Tools

  1. Add a method to client.py
  2. Add the tool function to the relevant tools/*.py file
  3. That's it — server.py never needs to change

Source: README.md at commit 0b726c8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts