Codemagic
Codemagic is a CI/CD platform focused on mobile app development.
Verdict
Common use cases
- Check build status during standup
- Trigger release workflows from chat
- Clear caches after dependency updates
- Add new repos to CI pipeline
- Retrieve build artifacts for QA
Integration
- Vendor
- Codemagic
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 23
- Composio slug
codemagic
Tools
- Add Application from Private Repository
Tool to create an application from a private repository using SSH key authentication. Use when you need to add a new private repository to Codemagic with SSH credentials.
- Add New Application
Tool to add a Git repository to the applications list in Codemagic. Use when you need to add a new application to Codemagic from a repository URL.
- Delete All Application Cachesdestructive
Tool to delete all caches for a specific application. Use when clearing all cached data for an app. The deletion process is asynchronous and will complete after the API response is returned.
- Delete Specific Cachedestructive
Tool to delete a specific cache from an application. Use when a cached build artifact needs to be removed. The deletion is performed asynchronously and returns immediately with a 202 Accepted status.
- Get Account Info for Over-the-Air Updates
Tool to retrieve account information for over-the-air updates. Use when you need to check the account status (enabled/disabled/pending) and associated team identifier.
- Get All Builds
Tool to list all builds with optional filters for appId, workflowId, and branch. Use when you need to retrieve build history or search for specific builds. Supports pagination via the skip parameter.
- Get API Key
Tool to retrieve the API key for the authenticated user. Use when you need to fetch the API key associated with the current authentication token.
- Get Authenticated User
Tool to retrieve information about the currently authenticated user. Use when you need to get user ID, avatar URL, or check user permissions.
- Get Meta Information
Tool to get metadata about Codemagic including public IP addresses in use (in CIDR notation). Use when you need to retrieve IP blocks for whitelisting build machines or simulator network requests.
- Get Variable Group Information
Tool to retrieve information about a specific variable group including its name and configuration settings. Use when you need to get details for a variable group by its ID.
- Invite Team Member
Tool to invite a new team member to a Codemagic team. Use when you need to grant team access to a user. Requires team admin privileges. The 'developer' role corresponds to Member role and 'owner' role corresponds to Admin role in Codemagic
- List Team Apps
Tool to list all apps for a specific team in Codemagic. Use when you need to browse or retrieve team application information. Supports pagination via page and page_size parameters.
- List Variable Groups for App
Tool to retrieve paginated list of variable groups for an application. Use when you need to list or browse variable groups associated with a specific app.
- List Variables for Group
Tool to retrieve paginated list of variables for a specific variable group. Use when you need to list or browse environment variables within a variable group.
- Receive Webhook
Tool to receive webhook payloads from Git providers to trigger builds automatically. Use when repository events (commits, pull requests, tags) need to trigger Codemagic builds programmatically.
- Remove Team Memberdestructive
Tool to remove a collaborator from a Codemagic team. Use when you need to revoke team access for a specific user. The removal is performed asynchronously and returns immediately with a 202 Accepted status.
- Retrieve All Applications
Tool to retrieve all applications added to Codemagic. Use when you need to list or browse all applications in the Codemagic account.
- Retrieve an Application
Tool to retrieve a single application by its unique identifier. Use when you need to get application details including name, branches, and workflow configuration.
- Retrieve Caches for Application
Tool to retrieve a list of caches for a specific application. Use when you need to view cached data, check cache sizes, or manage application storage.
- Start New Build
Tool to start a new build for an application with specified workflow and branch or tag. Use when you need to trigger a build programmatically. Either branch or tag parameter must be provided.
- Stop Preview
Tool to stop an app preview. Use when you need to stop a running app preview by its identifier.
- Update Variable Group
Tool to change a variable group's name and security settings. Use when you need to update an existing variable group by its ID. Returns success confirmation on 204 No Content response.
- Update Variable in Group
Tool to update an existing variable within a specified variable group in Codemagic. Use when you need to modify a variable's name, value, or secure status.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations section. 2. Click 'Add Integration' and select Codemagic from the developer tools category. 3. Open your Codemagic account settings, navigate to the API integrations page, and generate a new API key with read and write permissions. 4. Copy the API key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will verify the key by fetching your user profile — you'll see a green checkmark when authentication succeeds. 6. Open any Space, type '@Codemagic get all builds' and send the message to confirm the integration works. 7. If the MCP returns a list of recent builds, you're ready to invoke other tools; if it fails, double-check the API key has the correct scopes and hasn't expired.
What teammates see: by default, memories from Codemagic are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Recent Build Status
@Codemagic get all builds for app ID 'abc123' and show the most recent five with their status and branch namesOpen in a Space →
Add Repository
@Codemagic add a new application from the repository URL 'https://github.com/myteam/mobile-app' and confirm it was added successfullyOpen in a Space →
Clear App Caches
@Codemagic delete all caches for application ID 'xyz789' to force a clean build on the next runOpen in a Space →
OTA Update Status
@Codemagic get account info for over-the-air updates and tell me if it's enabled and what the team ID isOpen in a Space →
User Permissions Check
@Codemagic get authenticated user details and show me the user ID and avatar URLOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Codemagic show me all builds for the mobile-app repository from the last week, filtered by the production workflow
Here are the recent builds for mobile-app (production workflow): • Build #847 (main branch) - Success - Completed 2 hours ago - Duration: 8m 32s • Build #846 (main branch) - Failed - Completed 1 day ago - Duration: 3m 12s (failed at test stage) • Build #843 (release/v2.1 branch) - Success - Completed 3 days ago - Duration: 9m 45s • Build #841 (main branch) - Success - Completed 5 days ago - Duration: 8m 18s This is an illustrative example based on typical build history data. Your actual results will vary by repository activity and workflow configuration.
This example demonstrates read-only access to build history with filtering. Requires an API key with read permissions. The Get All Builds tool supports pagination—if you have high build volume, results may be truncated and require multiple queries with the skip parameter to retrieve complete history.
@Codemagic add the new backend-services repository from github.com/ourteam/backend-services to our Codemagic applications
Successfully added backend-services to your Codemagic applications. Application ID: 64f8a2b1c9e7d3001a4f5e89 Repository: github.com/ourteam/backend-services Status: Ready for configuration Next steps: Configure build workflows in the Codemagic UI or via codemagic.yaml in your repository. This is an illustrative example—actual application IDs and setup requirements depend on your repository structure and authentication method.
This example shows the Add New Application action, which modifies your Codemagic account state. If adding a private repository, you'll need SSH key authentication (use the Add Application from Private Repository tool instead). The MCP creates the application entry but doesn't configure workflows—you'll need to set those up separately in Codemagic's interface or config files.
@Codemagic check all failed builds from the last 3 days across our apps and summarize the most common failure patterns
Analyzed 47 builds across 6 applications from the last 3 days. Found 12 failures with these patterns: **Test Stage Failures (7 builds)**: Unit test timeouts in mobile-app and web-dashboard, primarily on the integration-tests workflow. Suggests flaky network-dependent tests. **Dependency Resolution (3 builds)**: CocoaPods version conflicts in ios-client builds. All occurred after the main branch merged PR #234. **Build Timeout (2 builds)**: backend-services builds exceeded 30-minute limit during Docker image creation on the staging workflow. This synthesis combines build data retrieval with AI analysis—actual patterns depend on your specific failure logs and build configurations.
This example pairs Codemagic's build history API with the AI's pattern-recognition capabilities. The MCP retrieves raw build data (status, duration, workflow), then the AI identifies trends. Note that detailed failure logs aren't always available via API—some analysis may require clicking through to the Codemagic UI for stack traces or console output.
Use-case deep-dives
When Codemagic beats Jenkins for iOS/Android CI at startup scale
A 3-person mobile team shipping weekly iOS and Android builds hits the Codemagic sweet spot. The Add Application from Private Repository tool connects your GitHub repo in under two minutes—no Jenkins YAML archaeology required. The Get All Builds filter lets your PM check release status without SSHing into a build server, and Delete Specific Cache unblocks a stuck workflow faster than restarting a Docker container. This MCP is the right call if your team ships native mobile apps and nobody wants to maintain build infrastructure. If you're web-only or already running Fastlane on your own metal, the 23-tool surface area is overkill. For teams under 10 devs doing React Native or Flutter, this integration turns build monitoring into a Slack thread instead of a DevOps ticket.
How customer success uses this MCP to debug app submission blockers
A 2-person support team at a mobile dev agency fields "my build failed" tickets from 15 client projects. The Get All Builds tool filtered by appId and branch surfaces the exact failure log without asking the client for screenshots. Get Account Info for Over-the-Air Updates confirms whether a client's OTA setup is misconfigured before escalating to engineering. This scenario works because Codemagic's API exposes build metadata that support can read without repo access. The trade-off: if your clients use CircleCI or GitHub Actions instead, this MCP is useless—it only sees Codemagic-managed builds. For agencies running client CI through one platform, this turns a 20-minute ticket into a 3-minute Slack reply.
When this MCP speeds up repo setup for product studios
A 6-person product studio spins up 4 new client projects per quarter, each needing iOS and Android CI from day one. The Add New Application tool scripted into their onboarding checklist cuts repo setup from 30 minutes of clicking through Codemagic's UI to a single API call. Get Authenticated User confirms the API key belongs to the right team account before provisioning. This is the right play if you onboard repos frequently and want setup to be a script, not a Notion doc. If you launch one project per year, the manual UI is faster than writing the automation. For studios billing setup time or running templatized client work, this MCP turns CI provisioning into a line item instead of a meeting.
Frequently asked
What does the Codemagic MCP do in Switchy?
It lets your team trigger mobile app builds, check build status, and manage Codemagic applications directly from Switchy's AI workspace. You can add repositories, delete caches, list builds by branch or workflow, and retrieve account info without opening the Codemagic dashboard. Useful when you want build visibility in the same place you're discussing deployments or debugging.
Do I need a Codemagic API key to connect this MCP?
Yes. The MCP uses API key authentication, which you generate in your Codemagic account settings. The key grants access to all 23 tools, including adding apps from private repositories and deleting caches. Anyone on your team with a valid Codemagic API key can connect the MCP to their Switchy workspace.
Can the Codemagic MCP start a new build or only check existing ones?
The MCP can list and filter builds by app, workflow, or branch, but it doesn't include a tool to start new builds. You'll still trigger builds through Codemagic's web UI, Git push hooks, or their separate REST API. This MCP is for visibility and app management, not build orchestration.
Why use this MCP instead of Codemagic's web dashboard?
The MCP surfaces build history and app config inside Switchy's AI workspace, so you can ask questions like "show me failed builds on the staging branch" without context-switching to Codemagic. It's faster for teams who already live in Switchy and want build data alongside code reviews or incident threads. The dashboard still wins for detailed logs and advanced settings.
Who on the team should connect the Codemagic MCP?
Anyone who needs to check build status or manage Codemagic apps. Typically mobile engineers, DevOps, or release managers. Each person connects their own API key, so permissions match their Codemagic role. The MCP doesn't consume Switchy plan limits beyond standard workspace usage.