Bitrise MCP server

What the model can do

Bitrise mobile CI/CD: projects (apps) and their repositories, builds with status, branch, commit, workflow, duration and credits used, pipelines, the workflows a project has run, build artifacts, pull-request builds waiting for approval, and quarantined tests. Logs and secrets are never read. When you ask, can start a build or pipeline, rebuild or abort one, approve or reject a waiting pull-request build, and quarantine or release a flaky test.

Reads

• bitrise_list_appsBitrise projects (apps) this token can see: slug, title, platform (ios, android, flutter…), repository, owner workspace, public or disabled.
• bitrise_list_buildsBitrise builds, newest first: number, status, workflow, branch or tag, short commit, pull request, when it was triggered, started and finished…
• bitrise_get_buildOne Bitrise build in full (except its log): status, abort reason, workflow, branch, commit, pull request, timings, machine, stack and credits.
• bitrise_list_pipelinesPipelines and standalone builds of a Bitrise project, newest first: id, number, status, workflow, branch, commit, timings…
• bitrise_list_workflowsThe workflow names a Bitrise project has ever run (which may include ones no longer in its bitrise.yml).
• bitrise_list_artifactsFiles a Bitrise build produced (APK, IPA, test reports…): title, type, size and whether its public install page is on.
• bitrise_list_build_requestsPull-request builds of a Bitrise project waiting for someone to approve them (from forks or untrusted contributors): request slug…
• bitrise_list_quarantined_testsTests quarantined on a Bitrise project (left out of test runs), oldest first: id, test and suite names, class…

Acts, when you ask

These change something in Bitrise. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• bitrise_trigger_buildStarts a Bitrise build or pipeline for a project on the branch, tag or commit given, running the workflow or pipeline named…
• bitrise_abort_buildAborts a running Bitrise build; it cannot be resumed (rebuild instead).
• bitrise_rebuildRebuilds a finished Bitrise build with the same parameters and workflow as a new build; it spends credits and may deploy if the workflow does.
• bitrise_abort_pipelineAborts a running Bitrise pipeline and its workflows; it cannot be resumed.
• bitrise_rebuild_pipelineRebuilds a Bitrise pipeline, the whole of it or (partial) only its unsuccessful workflows and those after them; it spends credits and may deploy.
• bitrise_decide_build_requestApproves (which starts the build and spends credits) or rejects a pull-request build waiting for approval on Bitrise.
• bitrise_quarantine_testQuarantines a test on a Bitrise project so failures of it stop failing builds, on every branch and workflow unless branches or targets narrow it…
• bitrise_unquarantine_testReleases a test from quarantine on a Bitrise project, so its failures fail builds again.

Connect it

First connect Bitrise on Dashboard → Connections, then add Memtro to your client once. The Bitrise tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Bitrise connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Why did last night's iOS build fail?
• › How many credits did the release workflow use this week?
• › Which pull-request builds are waiting for approval?
• › Which tests are in quarantine on the Android app?
• › Rebuild the last failed build on the main branch.

Questions

Is this an official Bitrise MCP server?

No. It is Memtro's MCP server with Memtro's Bitrise connector behind it: the connector reads Bitrise through its API with the credentials you connect on Dashboard → Connections, and Bitrise publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Bitrise?

Only when you ask, and only what it has been granted: start a build or pipeline on a branch, tag, commit, workflow or pipeline (spends credits); abort a running build; rebuild a finished build (spends credits); abort a running pipeline; rebuild a pipeline, whole or from its failed workflows (spends credits); approve or reject a pull-request build waiting for approval; quarantine a flaky test; release a test from quarantine. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server