Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 7
- 4 5
- 3 0
- 2 0
- 1 0
Trust in production
- Trust it - 100%
- With caveats - 0%
- Wouldn't - 0%
100% would recommend this server
How reviewers scored it
- Setup & docs 4.7
- Auth experience 4.4
- Reliability 4.3
- Maintainer responsiveness 4.6
Why it got an A
Buildkite's own MIT-licensed server, which also runs the hosted endpoint. OAuth is the default, tokens last an hour, and a /readonly path issues a token with read scopes only; toolsets can be narrowed by URL or header. Very active, with weekly releases, several maintainers and no advisories on record, so it earns full marks. Main caution: build logs and annotations can carry text from pull requests, and the standard endpoint can create pipelines and trigger or cancel builds. Read-only MCP does not stop an agent using an authenticated bk CLI.
How to connect
// ~/.cursor/mcp.json (read-only endpoint, selected toolsets)
{ "mcpServers": { "buildkite-read-only-toolsets": { "url": "https://mcp.buildkite.com/mcp/readonly",
"headers": { "X-Buildkite-Toolsets": "user,pipelines,builds" } } } }// mcp.json
{ "servers": { "buildkite": { "url": "https://mcp.buildkite.com/mcp", "type": "http" } } }claude mcp add --transport http buildkite https://mcp.buildkite.com/mcpIs Buildkite MCP Server safe?
Is Buildkite MCP Server safe to use?
Buildkite MCP Server grades A: all four checks are at full marks. Strong public trust signals. It is still not a full audit, so give it the narrowest access that works.
Does Buildkite MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Buildkite MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Dynatrace Remote MCP ServerDynatrace's hosted MCP server, running inside your Dynatrace SaaS environment, to run and explain DQL, look into problems, vulnerabilities and Kubernetes events, and forecast time series.
- A GitHub MCP ServerOfficial GitHub server for repos, issues, pull requests, Actions, and code security, hosted or local.
- A GitLab MCP ServerGitLab's built-in MCP server for projects, merge requests, work items, code, and CI pipelines, on GitLab.com or your own instance.
- A Honeycomb MCPHoneycomb's hosted MCP server to query datasets, read traces, run BubbleUp, and read or change boards, triggers and SLOs, with per-resource OAuth scopes.
Embed this badge
[](https://trustedmcp.io/servers/buildkite-mcp-server)<a href="https://trustedmcp.io/servers/buildkite-mcp-server"><img src="https://trustedmcp.io/badge/buildkite-mcp-server.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Trustworthy enough for real work
Set this up for our team after comparing a few options. Auth is handled properly, and revoking access later was one click. Updates land regularly, and nothing broke when I upgraded. Narrowing the scopes took ten minutes and made me much happier running it. Would recommend without hesitation.
Used for Debugging sessions in Cursor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Quietly reliable
Tried it on a side project first, then rolled it out at work. Updates land regularly, and nothing broke when I upgraded. Auth is handled properly, and revoking access later was one click. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent.
Used for Keeping project tickets in sync with code changes
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Set it up once, forgot about it
Replaced a homegrown script with Buildkite MCP Server and have not looked back. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Good choice if you need Buildkite in your agent.
Used for Generating boilerplate from existing patterns
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Solid and well behaved
Been running this for about a month now. Scoped the token to just what the agent needs and it respected that.
Used for Code review summaries for pull requests
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Better than the DIY script it replaced
I use this almost daily. Token setup is the fiddliest part, after that it is smooth. Auth is handled properly, and revoking access later was one click. Easy recommendation.
Used for Scripting routine maintenance tasks
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Recommended it to two teams already
Our agents call this dozens of times a day. Turned on read-only mode on day one, highly recommend doing the same. I like that access goes through a proper sign-in instead of a long-lived secret on disk. It is in our production agent and I sleep fine.
Used for Automating release notes
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Good defaults, good docs
Simple to set up in Cursor, simple to reason about. The scope options are worth reading carefully, the defaults are broader than I wanted. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Releases come often and the changelog is clear. Good choice if you need Buildkite in your agent.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Surprisingly polished
Started with it as an experiment, now it is a fixture. Sign-in flow was painless and I never had to paste a key into a config file. Happy to run it in production.
Used for Internal developer assistant
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
No complaints after a month
Installed it on a Friday, it was part of my workflow by Monday. I like that access goes through a proper sign-in instead of a long-lived secret on disk. You can tell it is actively maintained, the rough edges keep getting fixed.
Used for Letting a coding agent open and triage issues
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Earned a permanent spot in my config
Clear tool names, sensible outputs, very few surprises. Sign-in flow was painless and I never had to paste a key into a config file. Happy to run it in production.
Used for CI failure investigation
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
The Buildkite integration I wanted
Of the Buildkite integrations I tried, this one is the most predictable. Used a fine-grained token with short expiry and it works fine with that. Releases come often and the changelog is clear. Sign-in flow was painless and I never had to paste a key into a config file.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 4/5
Does what it says, no drama
Hooked Buildkite MCP Server into Claude Code and it worked on the first try. Scoped the token to just what the agent needs and it respected that. Read-only mode is the first thing I enable, and it covers most of what I need. It is in our production agent and I sleep fine.
Used for Looking up Buildkite data without leaving the editor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.