Labsco
MCP SERVER

CodemagicMcp

by AgiMaulana

Trigger a Codemagic build, follow its steps, read the failing log and grab the artifact — without leaving the chat.

Build Systems & CI/CD
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.