Codemagic MCP Server

What is Codemagic MCP Server?

A lightweight, community-maintained Model Context Protocol (MCP) server that provides seamless access to Codemagic CI/CD APIs. Designed for agents, AI-native workflows, and MCP-compatible clients.

How to use Codemagic MCP Server?

Clone the repository, set up your Codemagic API key, and configure the MCP server in your client (e.g., Claude Desktop) using the uv command with the appropriate path and environment variable CODEMAGIC_API_KEY.

Key features of Codemagic MCP Server

• Interact with Codemagic CI/CD using natural language
• Manage applications: list, add, get private apps
• Handle builds: start, list, check status, cancel
• Download artifacts and create public artifact URLs
• View and clear application caches
• Invite or delete team members

Use cases of Codemagic MCP Server

• List all applications on Codemagic via a chat interface.
• Start a new build for a Flutter app using natural language commands.
• Retrieve artifacts from the latest build automatically.
• Check cache usage and clear app caches as needed.

FAQ from Codemagic MCP Server

What does Codemagic MCP Server do?

It wraps Codemagic REST API endpoints into MCP tools, enabling AI assistants to manage CI/CD workflows using natural language.

What are the runtime dependencies?

Python 3.10+ and the mcp[cli] and requests packages. The server runs via uv.

Where does the data live and how is authentication handled?

All data stays within Codemagic’s APIs. Authentication requires a CODEMAGIC_API_KEY environment variable, set during client configuration.

What transport does the server use?

It uses standard MCP transport (stdio), as shown in the Claude Desktop configuration example.

Are there any known limitations?

The README does not mention specific limitations, but it is community-maintained and requires a valid Codemagic API key.