Install Bitrise MCP Server in Claude Applications
Claude Code CLIClick to copy link
PrerequisitesClick to copy link
- Claude Code CLI installed (recent version, with MCP OAuth support)
- A Bitrise account
- Open Claude Code inside the directory for your project (recommended for best experience and clear scope of configuration)
Remote Server Setup (Streamable HTTP) — RecommendedClick to copy link
The remote server uses OAuth to authenticate you against your Bitrise account. No token to copy or paste.
- Add the server:
claude mcp add --transport http bitrise https://mcp.bitrise.io
- Restart Claude Code.
- On the first tool use, Claude Code will open your browser to sign in. Log in to Bitrise (or confirm your existing session) and approve the consent screen.
- Run
claude mcp listto confirm the server is configured.
Fallback: PAT-based authenticationClick to copy link
If you're on a Claude Code version without MCP OAuth support, or you'd prefer to use a Personal Access Token:
- Create a Bitrise API Token under Account Settings → Security.
- Add the server with the token as a Bearer header:
claude mcp add --transport http bitrise https://mcp.bitrise.io -H "Authorization: Bearer YOUR_BITRISE_PAT"
Storing Your PAT Securely
For security, avoid hardcoding your token. One common approach:
-
Store your token in
.envfileBITRISE_PAT=your_token_here -
Add to .gitignore
echo -e ".env\n.mcp.json" >> .gitignore -
Reference it when adding:
claude mcp add --transport http bitrise https://mcp.bitrise.io -H "Authorization: Bearer $(grep BITRISE_PAT .env | cut -d '=' -f2)"
Local Server Setup (Go required)Click to copy link
The local server runs in stdio mode and authenticates with a Personal Access Token (no browser OAuth flow in stdio mode).
Prerequisites: Go (>=1.25) installed and a Bitrise PAT.
-
Run:
claude mcp add bitrise -e BITRISE_TOKEN=YOUR_BITRISE_PAT -- go run github.com/bitrise-io/bitrise-mcp/v2@v2With an environment variable:
claude mcp add bitrise -e BITRISE_TOKEN=$(grep BITRISE_PAT .env | cut -d '=' -f2) -- go run github.com/bitrise-io/bitrise-mcp/v2@v2 -
Restart Claude Code.
-
Run
claude mcp listto see if the Bitrise server is configured.
VerificationClick to copy link
claude mcp list
claude mcp get bitrise
Claude DesktopClick to copy link
PrerequisitesClick to copy link
- Claude Desktop installed (latest version)
- A Bitrise account
Configuration File LocationClick to copy link
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Remote Server setup (Streamable HTTP) — RecommendedClick to copy link
Recent Claude Desktop versions support MCP OAuth natively. See Claude | Connecting to a Remote MCP Server. On first connection, Claude Desktop opens your browser to authenticate with Bitrise — no token needed.
If your Claude Desktop version doesn't yet support remote MCP servers natively, you can use mcp-remote as an adapter:
{
"mcpServers": {
"bitrise": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.bitrise.io"
]
}
}
}
mcp-remote will handle the OAuth flow on your behalf. If your version of mcp-remote doesn't yet support OAuth, you can fall back to providing a PAT:
{
"mcpServers": {
"bitrise": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.bitrise.io",
"--header",
"Authorization: Bearer YOUR_BITRISE_PAT"
]
}
}
}
Save the config file and restart Claude Desktop. If everything is set up correctly, you should see a hammer icon next to the message composer.
In case npx is not found by Claude (ENOENT), specify the path to the npx binary in the env section:
{
"mcpServers": {
"bitrise": {
...
"env": {
"PATH": "PATH to bin of npx"
}
}
}
}
Local Server Setup (Go required)Click to copy link
The local server uses stdio with a Personal Access Token:
{
"mcpServers": {
"bitrise": {
"command": "go",
"args": [
"run",
"github.com/bitrise-io/bitrise-mcp/v2@v2"
],
"env": {
"BITRISE_TOKEN": "YOUR_BITRISE_PAT",
"PATH": "PATH to bin directory of go:PATH to directory of git",
"GOPATH": "your GOPATH",
"GOCACHE": "your GOCACHE"
}
}
}
}
Manual Setup StepsClick to copy link
- Open Claude Desktop
- Go to Settings → Developer → Edit Config
- Paste the code block above in your configuration file
- If you're navigating to the configuration file outside of the app:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Open the file in a text editor
- Paste one of the code blocks above, based on your chosen configuration (remote or local)
- Save the file
- Restart Claude Desktop
- If using OAuth: complete the sign-in flow in your browser the first time you use a tool
Advanced configurationClick to copy link
See Tools for enabling/disabling specific API groups.
TroubleshootingClick to copy link
OAuth flow doesn't open browser:
- Make sure your Claude version supports MCP OAuth (recent builds only)
- Try falling back to PAT-based authentication
Authentication Failed:
- For OAuth: re-authenticate via
/mcpcommand in Claude Code, or by deleting and re-adding the server - For PAT: check token hasn't expired or been revoked
Remote Server:
- Verify URL:
https://mcp.bitrise.io
Server Not Starting / Tools Not Showing:
- Run
claude mcp listto view currently configured MCP servers - Validate JSON syntax
- Restart Claude Code and check
/mcpcommand - Delete the Bitrise server by running
claude mcp remove bitriseand repeating the setup process with a different method - Check logs:
- Claude Code: Use
/mcpcommand - Claude Desktop:
ls ~/Library/Logs/Claude/andcat ~/Library/Logs/Claude/mcp-server-*.log(macOS) or%APPDATA%\Claude\logs\(Windows)
- Claude Code: Use
Important NotesClick to copy link
- Remote server requires Streamable HTTP support (check your Claude version). OAuth requires a more recent build than basic Streamable HTTP.
- Configuration scopes for Claude Code:
-s user: Available across all projects-s project: Shared via.mcp.jsonfile- Default:
local(current project only)