LABSCO SUMMARY

Vendor-run, OAuth-first, and you can cap how many tools it exposes.

The API-group filter is the practical detail: this server has a lot of tools, and a client with a tool-count limit can enable just apps and builds. OAuth means most modern clients sign in once with no token handling, and the release-management group is worth enabling on its own to avoid confusing it with the apps group, as the docs recommend.

What it is

Bitrise's own MCP server over the Bitrise API, covering app setup, build operations, artifacts, webhooks and release management, grouped into API groups you can enable selectively.

What you get

Apps — list_apps, register_app, get_app, get_bitrise_yml and update_bitrise_yml, plus list_branches
Builds — trigger_bitrise_build, get_build, abort_build, get_build_log and list_build_workflows
Artifacts — list_artifacts, get_artifact and delete_artifact
Webhooks — create_outgoing_webhook, list_outgoing_webhooks and their update/delete counterparts
Pipelines, cache items, workspaces, group roles and account tools
Release management — connected apps, installable artifacts, tester groups and CodePush deployments
Tool exposure limited by API group, via ENABLED_API_GROUPS locally or the x-bitrise-enabled-api-groups header remotely

Requirements

OAuth authentication — sign in once with your Bitrise account, no token to copy for clients that speak MCP OAuth. Clients that do not can pass a Bitrise Personal Access Token in the Authorization header. A hosted remote server runs at https://mcp.bitrise.io/ over streamable HTTP.

Setup effort

One command, then sign in — claude mcp add --transport http bitrise https://mcp.bitrise.io, then approve the OAuth sign-in

See installation options

USE CASES

01

Understanding why a build failed

Fetch the build and read its log without opening the Bitrise dashboard.

get_buildget_build_log

02

Kicking off a build from where you are

Trigger a build on the app and branch you name, then watch its status.

trigger_bitrise_buildget_build

03

Grabbing an artifact from a build

List the build's artifacts and pull the one you need.

list_artifactsget_artifact

04

Editing the pipeline config

Read the current bitrise.yml and update it in place.

get_bitrise_ymlupdate_bitrise_yml

05

Keeping the tool list manageable

Enable only the API groups you need through ENABLED_API_GROUPS rather than exposing everything.

81 tools

Listed in project docs. Your client may show a different list.

list_apps

register_app

finish_bitrise_app

get_app

delete_app

update_app

get_bitrise_yml

update_bitrise_yml

list_branches

register_ssh_key

register_webhook

list_builds

trigger_bitrise_build

get_build

abort_build

BEFORE YOU INSTALL

What to know first

Tools you get

81 tools named in the project's documentation. ENABLED_API_GROUPS (stdio) or the x-bitrise-enabled-api-groups header (HTTP) limits which groups load, and the read-only group gives a write-free subset. All groups are on by default.

Requires

A client that can reach a remote MCP server over HTTP

INSTALLATION

Connect your client

Server setup

Setup

Claude Code — go run

RECOMMENDED, no token: add the hosted remote server over Streamable HTTP and sign in with OAuth — Claude Code: claude mcp add --transport http bitrise https://mcp.bitrise.io, then restart; the browser opens on first tool use. VS Code: add {"servers":{"bitrise":{"type":"http","url":"https://mcp.bitrise.io"}}} to settings.

Claude Desktop without native remote-MCP support: use the mcp-remote adapter block from the Claude Desktop tab below in claude_desktop_config.json (macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json, Linux ~/.config/Claude/claude_desktop_config.json), then restart.

PAT fallback if your client lacks MCP OAuth: create a Bitrise API token at Account Settings -> Security, then claude mcp add --transport http bitrise https://mcp.bitrise.io -H "Authorization: Bearer <YOUR_BITRISE_TOKEN>"

LOCAL stdio server (requires Go >= 1.25 and a PAT):

TERMINAL

claude mcp add bitrise -e BITRISE_TOKEN=<YOUR_BITRISE_TOKEN> -- go run github.com/bitrise-io/bitrise-mcp/v2@v2

Verify with claude mcp list and claude mcp get bitrise

Optional: limit exposed tools with the ENABLED_API_GROUPS env var (local stdio) or the x-bitrise-enabled-api-groups HTTP header (remote)

Hosted endpoint

ENDPOINT URL

https://mcp.bitrise.io

Add this hosted endpoint to your MCP client, then sign in.

MCP Clients

Claude Code

CLAUDE CODE · TERMINAL

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

Claude Desktop

CLAUDE DESKTOP · JSON

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

VS Code

VS CODE · JSON

{
  "servers": {
    "bitrise": {
      "type": "http",
      "url": "https://mcp.bitrise.io"
    }
  }
}

Windsurf

WINDSURF · JSON

{
  "mcpServers": {
    "bitrise": {
      "serverUrl": "https://mcp.bitrise.io"
    }
  }
}

Gemini CLI

GEMINI CLI · JSON

{
  "mcpServers": {
    "bitrise": {
      "httpUrl": "https://mcp.bitrise.io"
    }
  }
}

GitHub Copilot

GITHUB COPILOT · JSON

{
  "servers": {
    "bitrise": {
      "url": "https://mcp.bitrise.io"
    }
  }
}

Kiro

Add power from GitHub:

KIRO · URL

https://github.com/bitrise-io/bitrise-mcp/tree/main/kiro-powers/bitrise-ci

Bitrise