How to connect the Bitrise MCP server

Before you start

• A Bitrise account. You can sign in or create one on the Bitrise sign-in page that opens during the OAuth flow; a Workspace is created for new accounts. docs.bitrise.io/en

Authentication

Your client → Bitrise MCP

OAuth sign-in, handled by your MCP client. docs.bitrise.io/endocs.bitrise.io/enmodelcontextprotocol.io/specification

Bitrise MCP → Bitrise API

The server acts on your account with the access you approve. docs.bitrise.io/endocs.bitrise.io/en

Steps

1. Open Bitrise's MCP setup instructions

   docs.bitrise.io/en/bitrise-platform/ai/onboarding-for-agents
2. Add the Bitrise MCP server to your client

   Add https://mcp.bitrise.io as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"), with no token. Reload the client so the change takes effect. Bitrise also ships a Cursor Marketplace plugin.

   docs.bitrise.io/endocs.bitrise.io/enregistry.modelcontextprotocol.io/v0.1
3. Sign in to Bitrise and approve the consent screen
   docs.bitrise.io/en
4. Optional: limit the enabled API groups
   registry.modelcontextprotocol.io/v0.1docs.bitrise.io/en
5. If your client can't use OAuth, use a personal access token

   Create a personal access token under Account settings, Security, and send it in the Authorization header as a bearer token. Use this for CI, scripts, or clients without MCP OAuth support. Keep the token in a secret store, not in shared configuration.

   docs.bitrise.io/endocs.bitrise.io/en
6. Only for the token alternative: Authorization
   registry.modelcontextprotocol.io/v0.1docs.bitrise.io/en
7. List the server's tools

   Your client should list the server's tools. That confirms the connection, not every API permission.

   docs.bitrise.io/en

What we observed

• 5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.bitrise.io/.well-known/oauth-protected-resource, which names the authorization server https://oauth.bitrise.io and header bearer tokens.