Connect Buildkite to Andromity with the Buildkite MCP server

Buildkite hosts an official remote MCP server at https://mcp.buildkite.com/mcp. With it, Andromity can look at your pipelines and builds, read logs and annotations, and summarize why a build failed while you fix the code.

Sign-in is OAuth with your Buildkite user account. Access tokens last 12 hours and refresh tokens last seven days.

What the agent can do with Buildkite

• Look up builds and pipelines.
• Read job logs and annotations.
• Summarize a failing build: problem jobs, log tails, annotations and failed tests (get_build_failure_summary, in the investigations toolset).
• Wait for a build to finish, checking for up to 45 seconds per call (wait_for_build).
• Review test results.

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Buildkite MCP server”.

• The CI build for this branch is red. Get the failure summary from Buildkite, find the cause in the diff and fix it.
• I just pushed a fix. Wait for the Buildkite build on this branch to finish and tell me whether it passed.
• Read the logs of the failed test job on the latest main build and write a regression test for the flaky case.

Connect Buildkite

1. You need a Buildkite user account with access to the organization.
2. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Buildkite and select Connect.
3. Sign in to Buildkite in your browser and approve the connection.
4. Andromity saves Buildkite to ~/.andromity/mcp.json and connects it.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• The OAuth token on https://mcp.buildkite.com/mcp has both read and write scopes. Write actions can run pipeline commands, including deployments.
• Buildkite documents a read-only OAuth endpoint, https://mcp.buildkite.com/mcp/readonly. To use it, add a server with that URL in mcp.json and sign in from its card.
• Buildkite notes that read-only MCP access restricts only that connection. An agent with shell access and its own bk CLI session can still make changes, so restrict that path separately.
• Buildkite advises requiring approval for writes. Andromity's permission modes apply to every tool call.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• Remote requests have their own rate limit, separate from your organization's REST API limit. Buildkite documents the values on its rate limits page.
• Remote endpoints update automatically and cannot be pinned to a version.
• Toolsets such as investigations, builds, logs, annotations and tests can be configured on the remote server. Enable investigations to get the failure summary.

Questions

Does Buildkite have an official MCP server?

Yes. Buildkite hosts a remote server at https://mcp.buildkite.com/mcp with OAuth, and also offers a local server.

Can I give the agent read-only access to Buildkite?

Yes. Use https://mcp.buildkite.com/mcp/readonly, which only exposes tools that need read scopes or no scope. Add it by hand in mcp.json.

Can the agent trigger deployments?

With the default endpoint the OAuth token has write scope, and Buildkite says write actions can run pipeline commands including deployments. Use the read-only endpoint if you do not want that.

Sources

This guide is based on Buildkite’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• Buildkite MCP server overview

Buildkite is a trademark of its owner. Andromity is not affiliated with or endorsed by Buildkite.