Buildkite MCP server

What the model can do

Buildkite CI: pipelines, builds by state, branch, commit, creator and date with their failed jobs, one build in detail, agents, a build's annotations and artifacts; when asked, can annotate a build, start, cancel or rebuild a build, retry, cancel, unblock or reprioritise a job, and archive a pipeline.

Reads

• buildkite_list_pipelinesBuildkite pipelines in the organisation: name, slug, repository, default branch and URL.
• buildkite_list_buildsBuildkite builds, newest first, across the organisation or for one pipeline: state, branch, commit, message, who triggered it, timings…
• buildkite_get_buildOne Buildkite build by pipeline and number: state, commit, message, creator, timings, job state counts and failed jobs.
• buildkite_list_agentsBuildkite agents in the organisation: name, hostname, connection state, version, queue tags and the job it is running.
• buildkite_list_annotationsAnnotations on one Buildkite build (test failure summaries, coverage notes, deploy links): context, style and text.
• buildkite_list_artifactsArtifacts uploaded by one Buildkite build: path, size, state and the job that made them.

Acts, when you ask

These change something in Buildkite. 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.

• buildkite_create_annotationAdd a new annotation (Markdown) to a Buildkite build, shown at the top of the build page.
• buildkite_create_buildStart a new build of a Buildkite pipeline on a commit and branch.
• buildkite_cancel_buildCancel a Buildkite build that is scheduled, running or failing; its running jobs are stopped.
• buildkite_rebuild_buildRebuild a Buildkite build as a new build with the same commit, branch, message and environment (not the branch's current head…
• buildkite_retry_jobRetry a failed or timed-out job in a Buildkite build, which runs it again on an agent.
• buildkite_cancel_jobCancel one job in a Buildkite build (scheduled, assigned or running).
• buildkite_unblock_jobUnblock a block step in a Buildkite build so the build carries on, which often releases a deploy.
• buildkite_reprioritize_jobChange the queue priority of a waiting Buildkite job (higher runs sooner).
• buildkite_archive_pipelineArchive a Buildkite pipeline: it becomes read-only and hidden from pipeline pages by default, and no new builds run.

Connect it

First connect Buildkite on Dashboard → Connections, then add Memtro to your client once. The Buildkite 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 Buildkite 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

• › Is main green on the api pipeline right now?
• › Why did the deploy build fail this morning, and which jobs failed?
• › Which agents are disconnected, and which queue are they on?
• › Retry the failed integration tests job on build 482 of the api pipeline
• › Add an annotation to build 482 saying the flaky checkout test is being fixed

Questions

Is this an official Buildkite MCP server?

No. It is Memtro's MCP server with Memtro's Buildkite connector behind it: the connector reads Buildkite through its API with the credentials you connect on Dashboard → Connections, and Buildkite 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 Buildkite?

Only when you ask, and only what it has been granted: add an annotation to a build; start a build of a pipeline on a commit and branch (runs CI); cancel a scheduled or running build; rebuild a build with the same commit, branch and message (runs CI); retry a failed job (runs CI); cancel one job; unblock a block step so the build continues, which can release a deploy; change a job's queue priority; archive a pipeline. 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