list_appsLABSCO SUMMARY
A red build gets diagnosed in the place you found out about it.
The path from a failed build to the specific step, its raw log and the artifact it did or did not produce is one continuous line here — which is the part of CI triage that usually costs the most clicks.
What it is
The Codemagic CI/CD REST API exposed as tools, covering apps, builds, artifacts, caches and environment variables. It is a local Python server that your client starts and stops with each session.
What you get
- Applications listed and inspected, with public repositories added directly and private ones added using an SSH key
- Builds listed and triggered, with details including a step count summary, and the full step list on request
- A step-by-step status summary of a build, filterable by status, so the failing step is found without reading the whole log
- Raw logs for a specific step, inline or written to a managed temporary file, with a check for whether that file still exists
- Build artifacts listed, their download URLs fetched, and a time-limited public URL created for sharing one
- Build caches and environment variables listed, with variables added and updated, and webhooks listed and added
Requirements
Python, and a Codemagic account — every tool here calls the Codemagic REST API on your behalf, so the account's access determines what you can see and change. Adding a private repository additionally needs an SSH key.
Setup effort
Build from source — git clone https://github.com/AgiMaulana/CodemagicMcp.git
USE CASES
01
Finding out why the build went red
Pull the build, read the step-by-step status summary filtered to failures, then take the raw log for just that step rather than the whole run.
02
Kicking off a build without opening the dashboard
Find the app in your account and trigger a build for it, then check back on its status from the same conversation.
03
Getting the binary to a tester
List the artifacts a build produced and create a time-limited public URL for the right one, so it can be shared without handing over account access.
04
Fixing a build that fails on configuration
Read the environment variables the app has, correct the wrong one or add the missing one, and trigger a fresh build to confirm.
05
Chasing a build that suddenly got slow
Look at the caches for the application alongside recent builds, which is where an unexpected slowdown usually turns out to live.
06
Onboarding a new repository
Add the repository — public directly, private with an SSH key — then wire up a webhook and confirm the app is registered as you expect.
25 tools
Listed in project docs. Your client may show a different list.
get_appadd_appadd_private_appdelete_applist_buildsget_buildtrigger_buildcancel_buildget_build_logsget_step_logsget_step_log_artifactlist_build_artifactsget_artifact_urlcreate_artifact_public_urllist_cachesdelete_cachedelete_all_cacheslist_variablesadd_variableupdate_variabledelete_variablelist_webhooksadd_webhookdelete_webhookBEFORE YOU INSTALL
What to know first
Tools you get
25 tools named in the project's documentation.
Requires
- Python 3.11+
- CODEMAGIC_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/AgiMaulana/CodemagicMcp.git
cd CodemagicMcp
python3 -m venv .venv
.venv/bin/pip install -e .MCP Clients
Claude Code, Claude Desktop
JSON
{
"mcpServers": {
"codemagic": {
"command": "<YOUR_PATH_TO_CODEMAGIC_MCP>/.venv/bin/codemagic-mcp",
"env": {
"CODEMAGIC_API_KEY": "<YOUR_CODEMAGIC_API_KEY>",
"CODEMAGIC_DEFAULT_APP_ID": "<YOUR_CODEMAGIC_DEFAULT_APP_ID>"
}
}
}
}
