Repository navigation
Conversation
![buildsworth-bk-app[bot]](https://avatars.githubusercontent.com/in/3010600?s=60&v=4){kind=small}
There was a problem hiding this comment.
The new guidance matches the documented local and remote options. I left one note about carrying a pinned tag through the linked setup steps.
Want to dig deeper?
Paste this into your agent to explore the findings from this review's Buildkite build:
Download the buildsworth logs from build 33372, then answer my questions about the findings.
Install the reading-buildsworth-logs skill to run this.
About buildsworth
Model: gpt-6-sol with xhigh thinking.
How to request a review: Comment @buildsworth-bk review on the PR, or request buildsworth-bk as a reviewer.
Risk labels (how buildsworth classifies risk) — buildsworth classifies risk itself from the diff. Unless repository policy already allows L2 approval, grant it by mentioning @buildsworth-bk (see approval ceiling and L2 approval grant):
- L1 — Low risk (dep bumps, docs/copy, lockfiles, small presentational fixes). buildsworth may approve by default.
- L2 — Standard risk (new UI, additive API fields, refactors). Approved only when repository policy or a verified grant allows it; otherwise comment-only.
- L3 — High risk (auth, migrations, payments, secrets, perf-critical pipeline paths). Human approval required unless repository policy explicitly allows L3 approval; per-PR grants cannot allow it.
|
|
||
| Buildkite provides both a [remote](#types-of-mcp-servers-remote-mcp-server) and [local](#types-of-mcp-servers-local-mcp-server) MCP server, both of which provide access to its [MCP server tools](/docs/apis/mcp-server/tools#available-mcp-tools). The remote MCP server supports OAuth authentication for interactive AI tools and [API token pass-through](#api-token-pass-through-remote-mcp-server) for headless agents. | ||
|
|
||
| The Buildkite MCP server is under active development. Tools or their behavior may change or be removed, including breaking changes. If you need continued access to a specific tool or behavior, [run the local server](/docs/apis/mcp-server/local/installing) with a versioned Docker image tag or a binary from a specific release. Buildkite-hosted remote endpoints update automatically and cannot be pinned to a version. |
There was a problem hiding this comment.
Non-blocking: The linked installation steps and AI-tool configuration examples use buildkite/mcp-server without a tag and --pull=always, so copying them still follows the latest release on each restart. A short note to replace that image with buildkite/mcp-server:<version> in both the run command and client configuration would make this pinning guidance easier to follow.
2 participants
The Buildkite MCP server is under active development, so the docs should not imply that its tools and behavior are stable across updates.
Add a short note explaining that breaking changes may occur and that users who need a particular tool or behavior can pin a locally run Docker image or release binary. Clarify that Buildkite-hosted remote endpoints update automatically and cannot be pinned.