How to add Bitrise MCP Server to Claude Desktop

Manage Bitrise apps, builds, artifacts, pipelines and releases from your AI assistant. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 39★ · http · oauth

Claude Desktop config for Bitrise MCP Server

claude mcp add --transport http bitrise https://mcp.bitrise.io

{
  "mcpServers": {
    "bitrise-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.bitrise.io"
      ]
    }
  }
}

Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.

Setup steps

1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
2Paste the Bitrise MCP Server config below under the top-level "mcpServers" key.
3Fill in any placeholder secrets (API keys, paths) in the snippet.
4Save the file, then fully quit and reopen Claude Desktop.
5Open a chat and confirm Bitrise MCP Server's tools appear under the 🔌 tools menu.

Before you start

A Bitrise account
An MCP client that supports Streamable HTTP (and MCP OAuth for the recommended remote setup), e.g. Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, or AWS Kiro
For the local stdio server: Go (>=1.25) installed and a Bitrise Personal Access Token (BITRISE_TOKEN)

What Bitrise MCP Server can do in Claude Desktop

list_apps

List all the apps available for the authenticated account.

register_app

Add a new app to Bitrise.

finish_bitrise_app

Finish the setup of a Bitrise app.

get_app

Get the details of a specific app.

delete_app

Delete an app from Bitrise.

update_app

Update an app.

get_bitrise_yml

Get the current Bitrise YML config file of a specified app.

update_bitrise_yml

Update the Bitrise YML config file of a specified app.

Security

The recommended remote server uses OAuth — you sign in to your Bitrise account in the browser and approve a consent screen on first tool use; no token to store. For PAT-based fallback, create a Bitrise API token under Account Settings -> Security and pass it as an Authorization: Bearer header; avoid hardcoding it (store it in a gitignored .env and reference it). The local stdio server requires a BITRISE_TOKEN environment variable. Tools include destructive operations (delete app, delete artifacts, abort builds, replace group roles, irreversible CodePush deletes), so review tool calls before approving.

Bitrise MCP Server + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Bitrise MCP Server config there under the "mcpServers" key and restart the client.

Is Bitrise MCP Server safe to use with Claude Desktop?

How do I authenticate?

The recommended remote server at https://mcp.bitrise.io uses OAuth: on first tool use your client opens a browser to sign in to Bitrise and approve a consent screen — no token to copy. For clients without MCP OAuth, you can pass a Bitrise Personal Access Token as an Authorization: Bearer header instead. The local stdio server uses a BITRISE_TOKEN environment variable.

Do I need to run anything locally?

No. The recommended setup is the hosted remote server over Streamable HTTP, so there is nothing to install. A local stdio server is available as an alternative and requires Go (>=1.25) plus a Bitrise PAT (run via `go run github.com/bitrise-io/bitrise-mcp/v2@v2`).

Which clients are supported?

Installation guides are provided for Claude Desktop and Claude Code, Cursor, VS Code, GitHub Copilot in JetBrains/Visual Studio/Eclipse/Xcode, Windsurf, Gemini CLI, and AWS Kiro.

View repo Full Bitrise MCP Server page