Bitrise MCP

What bitrise-io/bitrise-mcp MCP server does

The bitrise-io/bitrise-mcp MCP server connects an MCP-compatible AI client to the Bitrise API. Its documented scope includes Bitrise app management, build operations, artifact management, and additional API access. This lets an assistant retrieve Bitrise information and carry out supported account or workspace actions through conversational requests.

Example tasks include finding the most recent failed iOS build and explaining the failure, calculating the success rate for builds on a main branch over a selected period, and adding a team member to a workspace with an administrator role. The exact available operations and parameters are documented in the repository’s tool reference.

How it works

The server presents Bitrise API functionality as MCP tools that an AI client can call. The client sends a request expressed in natural language, and the relevant tool uses the connected Bitrise account to read or modify Bitrise resources.

Authentication is designed around OAuth: users sign in with their Bitrise account instead of manually copying a Personal Access Token. PAT authentication remains available for MCP clients that do not support MCP OAuth. The authentication method therefore depends partly on the capabilities of the client being used.

Setup and configuration

The repository provides separate installation instructions for Claude Desktop and Claude Code CLI, Cursor, Windsurf, VS Code, GitHub Copilot in several other IDEs, Gemini CLI, and AWS Kiro. Choose the guide matching the client where you want to use the server. The supplied material does not specify a universal package-manager command or a single configuration file, so setup details should be taken from the relevant client guide in the repository.

After setup, authenticate through the supported Bitrise OAuth flow when the client supports MCP OAuth. For clients without that capability, configure the PAT-based authentication method described by the project. Access is governed by the permissions of the connected Bitrise account.

Tools and capabilities

The bitrise-io/bitrise-mcp MCP server is described as providing comprehensive access to Bitrise APIs, including:

• App management
• Build operations
• Artifact management
• Additional Bitrise API resources
• Workspace team-member administration, including assigning an administrator role
• Build history and failure inspection

Tool parameter descriptions are maintained in the repository’s documentation, which should be consulted before constructing automated requests or relying on a specific operation.

Limitations and notes

The provided material does not enumerate every tool, define transport details, or state which Bitrise account plans support each operation. It also does not provide a standalone executable installation command. Treat the repository’s client-specific installation pages and tool documentation as the source of truth for those details.

Using the server requires access to a Bitrise account through OAuth or, where necessary, a Personal Access Token. The project directs support questions and issue reports to the Bitrise support portal, and use is covered by Bitrise’s privacy policy.