Bitrise · Cursor
Add the Bitrise MCP server to Cursor
Set up and manage mobile CI/CD on Bitrise: apps, builds and logs, artifacts, pipelines, release management and CodePush.
1. Add the server
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"bitrise": {
"url": "https://mcp.bitrise.io/"
}
}
}Scopes, env vars, OAuth and limits: Cursor MCP config guide
2. Sign in
Cursor prompts you to sign in the first time a remote OAuth server is used. Bitrise is hosted by Bitrise, so there is nothing to install or keep updated.
3. Try it
Ask Cursor for something Bitrise can do. Set up and manage mobile CI/CD on Bitrise: apps, builds and logs, artifacts, pipelines, release management and CodePush. Approve the first tool call and check the result before allowing write actions automatically.
- · Remote servers take a url; local servers take command and args.
- · Values can reference ${env:NAME} so secrets stay out of the file.
FAQ
- How do I add the Bitrise MCP server to Cursor?
- Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.
- Is this the official Bitrise MCP server?
- Yes. It is published by Bitrise as io.github.bitrise-io/bitrise-mcp in the official MCP registry.
- Does the Bitrise MCP server need an API key?
- It is a hosted server. Most hosted servers sign you in with OAuth the first time Cursor uses them; check Bitrise's docs for any plan or permission requirements.
Links
Bitrise in other clients
More developer tools for Cursor
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →
Reviewed Oct 21, 2026. Command generated from the registry record and checked against Cursor's documented syntax.