Bitrise MCP

Trigger and debug Bitrise mobile builds from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Bitrise MCP connector does

The Bitrise MCP server connects Claude to Bitrise, the mobile CI/CD platform for iOS, Android, Flutter and React Native apps. Anthropic's directory lists 83 tools for apps, builds, pipelines, artifacts, caches, workspaces, tester distribution and CodePush updates. Several delete, invite or change what users' devices download. Bitrise's read-only toolset limits the connection to reads.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Bitrise MCP tools (83)

  • abort_build
  • abort_pipeline
  • add_member_to_group
  • add_testers_to_tester_group
  • codepush_create_deployment
  • codepush_delete_deployment
  • codepush_delete_update
  • codepush_generate_update_upload_url
  • codepush_get_deployment
  • codepush_get_metrics
  • codepush_get_update
  • codepush_get_update_status
  • codepush_list_deployments
  • codepush_list_updates
  • codepush_patch_update
  • codepush_promote_deployment
  • codepush_rollback_deployment
  • codepush_update_deployment
  • create_connected_app
  • create_outgoing_webhook
  • create_tester_group
  • create_workspace_group
  • delete_all_cache_items
  • delete_app
  • delete_artifact
  • delete_cache_item
  • delete_outgoing_webhook
  • finish_bitrise_app
  • generate_installable_artifact_upload_url
  • get_app
  • get_artifact
  • get_bitrise_yml
  • get_build
  • get_build_bitrise_yml
  • get_build_log
  • get_build_steps
  • get_cache_item_download_url
  • get_connected_app
  • get_installable_artifact_upload_and_proc_status
  • get_pipeline
  • get_potential_testers
  • get_tester_group
  • get_testers
  • get_workspace
  • get_workspace_groups
  • get_workspace_members
  • invite_member_to_workspace
  • list_apps
  • list_artifacts
  • list_available_stacks
  • list_branches
  • list_build_distribution_version_test_builds
  • list_build_distribution_versions
  • list_build_workflows
  • list_builds
  • list_cache_items
  • list_connected_apps
  • list_group_roles
  • list_installable_artifacts
  • list_outgoing_webhooks
  • list_pipelines
  • list_tester_groups
  • list_workspaces
  • me
  • notify_tester_group
  • rebuild_pipeline
  • register
  • register_app
  • register_ssh_key
  • register_webhook
  • replace_group_roles
  • set_installable_artifact_public_install_page
  • step_inputs
  • step_search
  • trigger_bitrise_build
  • update_app
  • update_artifact
  • update_bitrise_yml
  • update_connected_app
  • update_outgoing_webhook
  • update_tester_group
  • validate_bitrise_yml
  • verify_registration

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The default toolset can change. Bitrise says it is not a stable contract. Name the toolsets you rely on in the URL.
  • No scope-level read/write split. The protected-resource document names https://oauth.bitrise.io and lists no scopes. Narrowing happens through toolsets, not the consent screen.
  • Deletes are in the default set. delete_app, delete_artifact, delete_cache_item and delete_all_cache_items are all there unless you choose a narrower toolset.
  • Store releases need an extra toolset. App Store and Google Play tools appear only with release-management-store-releases or all.
  • We did not read the tools. Our anonymous request returned a 401, so per-tool schemas and annotations here come from Bitrise's published reference, not the live server.
  • No rate limits are documented in Bitrise's MCP pages.

Frequently asked questions

How do I make the Bitrise MCP server read-only?

Connect with the read-only toolset in the URL, as https://mcp.bitrise.io/?toolset=read-only. Bitrise groups its tools into toolsets that you choose with the toolset query parameter or the x-bitrise-enabled-toolset header, and the read-only toolset adds the read tools of every other toolset. Bitrise warns not to combine it with a smaller set, because it brings those read tools along with it.

Why does the Bitrise connector have a different number of tools than the docs?

Because the tool count depends on which toolsets are enabled. Bitrise documents 88 tools in its default set and 136 with every toolset enabled, while Anthropic's directory lists 83. The directory URL carries no toolset parameter, so it gets the default set. Bitrise also says the default set is not a stable contract and may lose tools without a major version change.

Can I use a Bitrise personal access token instead of OAuth?

Yes. Bitrise says most clients, including Claude Code, sign in with OAuth on first use, but clients without MCP OAuth support can send a Bitrise Personal Access Token as an Authorization Bearer header. Create the token under Account Settings, then Security, in Bitrise, and keep it out of version control. Bitrise suggests storing it in a .env file that is git-ignored.

Which Bitrise MCP tools reach outside my Bitrise workspace?

Bitrise names them through the openWorldHint annotation. Inviting a workspace member emails an arbitrary address, outgoing webhooks send build events to any URL, install-page tools publish an install page on the public internet, and CodePush tools change what end-user devices download. Registering a webhook or SSH key writes to the app's git provider. Store-release tools reach TestFlight, the App Store and Google Play.

Sources

Use it in an agent

Put Bitrise MCP to work.

Connect Bitrise MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.