Get the FREE Ultimate OpenClaw Setup Guide →

bitrise

MCP Server for the Bitrise API, enabling app management, build operations, artifact management and more.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio bitrise-io-bitrise-mcp node server.js \
  --env BITRISE_TOKEN="Your Bitrise API token" \
  --env BITRISE_API_BASE="https://api.bitrise.io/v0.1"

How to use

This MCP server provides programmatic access to Bitrise via a REST-like interface, enabling you to manage apps, trigger builds, retrieve artifacts, and interact with Bitrise resources through the MCP framework. The server authenticates requests using a Bitrise API token, so you will need to provide a valid token (and the base API URL if you’re using a self-hosted or custom Bitrise instance). Once running, you can use the MCP client tooling to list apps, start builds, fetch build artifacts, and query build statuses using the same endpoints exposed by Bitrise, wrapped in MCP endpoints for consistency with other MCP servers. The included docs (notably docs/tools.md) describe parameter names and responses in detail, helping you integrate Bitrise operations into your automation pipelines.

How to install

Prerequisites:

  • Node.js (v14+ recommended) and npm installed on your system
  • Access to a Bitrise API token with the required permissions
  1. Clone the MCP Bitrise server repository: git clone https://github.com/your-org/bitrise-io-bitrise-mcp.git cd bitrise-io-bitrise-mcp

  2. Install dependencies: npm install

  3. Configure environment variables:

    • Create a .env file or export variables in your environment: export BITRISE_TOKEN="<your_bitrise_token>" export BITRISE_API_BASE="https://api.bitrise.io/v0.1"
  4. Run the server: npm start

    or if using a direct node invocation

    node server.js

  5. Verify the server is running by sending a test request to the MCP endpoint (as per your MCP client usage documentation).

Additional notes

Tips and common issues:

  • Ensure your Bitrise token has the necessary scopes for the operations you plan to perform (apps, builds, artifacts).
  • If you use a self-hosted Bitrise instance, set BITRISE_API_BASE to its base URL (including the version path).
  • Rate limits from Bitrise apply; implement retry logic in your MCP client where appropriate.
  • Keep dependencies up to date to avoid breaking changes in the Bitrise API wrapper.
  • Review docs/tools.md within the repository for detailed parameter descriptions for each available endpoint (apps, builds, artifacts, etc.).

Related MCP Servers

Sponsor this space

Reach thousands of developers