Bitrise MCP: mobile CI/CD in a conversation with an agent
bitrise-mcp
The official Bitrise server shows the agent iOS and Android builds, artifacts, pipelines and releases, with OAuth sign-in
- 43 ★ on the repository
- Last commit
Broad access
Why this level
- The agent gets access to the Bitrise workspace: it can start builds, change webhooks, members and their roles
- Build logs and artifacts can hold secrets and user data, and they enter the model context
Install
- Works in
Manual install
claude mcp add --transport http bitrise "https://mcp.bitrise.io/?toolset=all"The remote server with OAuth sign-in; restart Claude Code after adding it.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent gets access to the Bitrise workspace: it can start builds, change webhooks, members and their roles
- Build logs and artifacts can hold secrets and user data, and they enter the model context
This is third-party code. Review the repository files before installing.
What it does
The server gives the agent access to the Bitrise API: apps, builds, artifacts, outgoing webhooks, cache items, pipelines, group roles, workspaces, release management, CodePush, store releases and insights. Tools are split into groups, and the toolset parameter selects the ones needed, such as apps, builds and workspaces, or all for everything. The connection goes to the remote server mcp.bitrise.io over Streamable HTTP. Sign-in is OAuth in the browser, so no personal token needs to be copied; a token stays as a fallback for clients without OAuth. For a local run there is a Go stdio mode with a token. Each tool documents its parameters and output schema.
Who it is for. Mobile developers and DevOps engineers whose apps build on Bitrise and who need to investigate failed builds and releases through an agent
Good fit when
- You need to see why the last iOS build failed and read the step log
- You want the success rate of main branch builds over the last week
- You need to fetch build artifacts or look at what sits in the cache
- A member has to be added to the workspace as an admin
- You want to start a build or pipeline on a branch without opening the web UI
Not a fit when
- The project builds somewhere other than Bitrise: the server works only with this service API
- You need read-only access: management tools can be trimmed with toolset, but token rights stay as they are
- You need to edit the build YAML in the repository: the server works only with the API and does not see project files
- The client supports neither remote MCP nor OAuth and you do not want to hand out a token
Example request
Show my last failed iOS build, explain from the log which step it stopped at and suggest what to fix.MCP
- Authentication
- OAuth
Environment variables
BITRISE_PATsecret- A personal Bitrise token for clients without OAuth, sent in the Authorization header
Limitations
The client needs MCP OAuth support or a Bitrise token in the Authorization header. The local mode requires Go 1.25 or newer. The default tool set is smaller than the full one, and all groups are enabled with toolset=all. Token rights set what the agent can see and change, so for read-only work issue a token with minimal rights and revoke it after the work. The last commit was made on November 5, 2026.
How to disable. Run claude mcp remove bitrise and revoke the grant in the Bitrise account settings. If you used a personal token, delete it on the account security page.
FAQ
Do I need to create a personal token?
No. Modern clients sign in through OAuth in the browser; a token is needed only for clients without MCP OAuth support.
What does the toolset parameter do?
It selects tool groups, for example apps, builds and workspaces, and the value all enables everything.
Can I run the server locally?
Yes, in stdio mode with Go 1.25 or newer and a personal Bitrise token.
Which clients does the documentation cover?
VS Code, JetBrains and other IDEs with Copilot, Claude Desktop and Claude Code, Cursor, Windsurf, Gemini CLI and AWS Kiro.
Where is data handling described?
Use of the server is governed by the Bitrise privacy policy, linked in the README.
Discussion
No questions or reviews yet.
Related
MCP serversBuildkite MCP Server
buildkite-mcp-server
Official Buildkite MCP server: pipelines, builds, jobs, logs and test results for the agent
Measure MCP: an agent reads mobile app crashes, ANRs, traces, sessions and bug reports and looks for the root cause.
A community MCP server for Azure DevOps work items, code and builds, with PAT authentication for on-premises Azure DevOps Server
A plugin that turns Jenkins into an MCP server so an agent can inspect jobs and build logs, trigger builds and read test results.
Azure DevOps MCP server
Azure DevOps MCP Server
Official Microsoft MCP server for Azure DevOps: work items, repositories, builds, test plans, and wiki from the agent
A Bitbucket Cloud MCP server with six generic tools that reach any repository or pull request REST API path
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Bitrise MCP: mobile CI/CD in a conversation with an agent (this card) | yes | OAuth | 43 | |
| MCP Server Plugin for Jenkins | yes | API key | 119 | a Jenkins plugin for self-hosted build servers, while this is the cloud mobile CI of Bitrise |
| GitLab MCP Server | no | API key | 2,101 | GitLab repositories and pipelines, while this covers builds, CodePush and releases of mobile apps |
README in short
The short README lists features, links to instructions for eight clients, gives three example prompts and links to support and the privacy policy. The details are in the docs folder: tools by group, output schemas and tool annotations.