Bitrise
Let your coding agent manage Bitrise apps, runs, and artifacts when you ship mobile or cross-platform apps from the terminal.
Overview
Bitrise MCP is an MCP server for the Ship phase that lets agents manage Bitrise apps, trigger builds, and handle artifacts over authenticated streamable HTTP.
What is this MCP server?
- Streamable HTTP MCP at mcp.bitrise.io with Bearer Personal Access Token auth
- Optional x-bitrise-enabled-api-groups header to scope apps, builds, workspaces, and other API groups
- App management, build operations, and artifact retrieval from one protocol surface
- Version v2.4.1 with GitHub source at bitrise-io/bitrise-mcp
- Fits solo builders already on Bitrise for iOS, Android, or Flutter shipping
- Server version v2.4.1
- Remote endpoint https://mcp.bitrise.io/ (streamable-http)
- Configurable API groups via x-bitrise-enabled-api-groups header (e.g. apps, builds, workspaces)
Community signal: 38 GitHub stars.
What problem does it solve?
Checking build status and downloading IPAs or APKs from Bitrise breaks your flow when you live inside an AI coding agent.
Who is it for?
Indie mobile or multi-stack builders who already use Bitrise and want agent-driven build and artifact operations during release week.
Skip if: Teams with no Bitrise account, or builders who only need local unit tests without a remote CI service.
What do I get? / Deliverables
After registration, your agent can query apps, run builds, and manage artifacts on Bitrise without leaving the editor or CLI session.
- Agent-callable Bitrise app and workspace operations
- Build trigger and status visibility from the agent session
- Artifact access aligned with enabled Bitrise API groups
Recommended MCP Servers
Journey fit
Bitrise is where releases become runnable binaries; the canonical shelf is ship because builders install this MCP to execute and monitor builds, not to brainstorm product ideas. Launch subphase covers build triggers, release candidates, and pre-store validation—the core Bitrise workflow for indie app makers.
How it compares
Remote CI MCP integration, not a local Xcode or Gradle skill or a generic testing framework.
Common Questions / FAQ
Who is Bitrise MCP for?
Solo and small-team builders on Bitrise who want Claude Code, Cursor, or other MCP hosts to run app, build, and artifact workflows from chat or the terminal.
When should I use Bitrise MCP?
Use it when you are shipping or operating mobile or multi-platform apps and need the agent to inspect pipelines, start builds, or fetch artifacts instead of copying URLs into the Bitrise dashboard.
How do I add Bitrise MCP to my agent?
Add the remote URL https://mcp.bitrise.io/ with Authorization set to Bearer plus your Personal Access Token from https://app.bitrise.io/me/account/security, and optionally set x-bitrise-enabled-api-groups for scoped API access.