Skip to main content

Install Bitrise MCP Server in VS Code

PrerequisitesClick to copy link​

  • VS Code installed (recent version, with MCP OAuth support)
  • A Bitrise account
  • For local setup: Go (>=1.25) installed and a Bitrise PAT

Remote Server Setup (Streamable HTTP) — RecommendedClick to copy link​

VS Code's MCP integration handles OAuth automatically. On first connection it'll open your browser to sign you in to Bitrise — no token needed.

Follow VS Code | Add an MCP server and add the following to your settings:

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

Save the configuration. VS Code will recognize the change, prompt you to sign in via your browser on first tool use, and load the tools into Copilot Chat.

Fallback: PAT-based authenticationClick to copy link​

If your VS Code build doesn't support MCP OAuth yet, you can use a Personal Access Token:

{
  "servers": {
    "bitrise": {
      "type": "http",
      "url": "https://mcp.bitrise.io",
      "headers": {
        "Authorization": "Bearer ${input:bitrise-token}"
      }
    }
  },
  "inputs": [
    {
      "id": "bitrise-token",
      "type": "promptString",
      "description": "Bitrise token",
      "password": true
    }
  ]
}

Create a Bitrise API Token under Account Settings → Security when prompted.

Local Server Setup (Go required)Click to copy link​

Local stdio mode authenticates with a Personal Access Token:

{
  "servers": {
    "bitrise-local": {
      "type": "stdio",
      "command": "go",
      "args": [
        "run",
        "github.com/bitrise-io/bitrise-mcp/v2@v2"
      ],
      "env": {
        "BITRISE_TOKEN": "${input:bitrise-token}"
      }
    }
  },
  "inputs": [
    {
      "id": "bitrise-token",
      "type": "promptString",
      "description": "Bitrise token",
      "password": true
    }
  ]
}

Advanced configurationClick to copy link​

See Tools for enabling/disabling specific API groups.