Buildkite MCP Server
Buildkite organizations, pipelines, builds, and jobs accessible via MCP.
Data last scanned today · Reviewed today
Overview
The Buildkite MCP Server acts as a bridge for AI assistants to query your CI/CD pipeline data directly. It provides a suite of endpoints to list organizational resources, retrieve build statuses, and filter for specific job outcomes like failures. By configuring the server with a Buildkite API token, users can programmatically inspect pipeline health and monitor deployment processes through natural language interfaces. The server supports integration through various MCP clients, including a simplified configuration flow for Cursor. Once integrated, the server allows AI models to fetch comprehensive details about specific build jobs or list entire pipelines, streamlining the process of troubleshooting failed builds or auditing CI/CD activity.
Our verdict
This server receives a security score of 10/100, indicating a high-risk level. The project is community-maintained with no official affiliation, and it lacks a software license, which creates ambiguity regarding permitted use. Furthermore, the repository has not seen a commit in over 484 days, suggesting it may be unmaintained. Given these factors, developers should exercise significant caution and review the codebase thoroughly before deploying it in any environment containing sensitive access credentials.
- Provides specific endpoints for retrieving build and pipeline metadata.
- Features a small footprint with only 4 direct dependencies.
- Includes documented support for easy integration within Cursor.
- High security risk score of 10/100.
- No detected open source license for usage.
- Project has not been updated in over 484 days.
- Single-contributor project with no official vendor support.
Setup
{
"mcpServers": {
"buildkite-mcp": {
"args": [
"-y",
"@drew-goddyn/buildkite-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| mcp_buildkite_list_organizations | List all Buildkite organizations. | low |
| mcp_buildkite_list_pipelines | List pipelines for a given organization. | low |
| mcp_buildkite_list_builds | List builds for a specific pipeline. | low |
| mcp_buildkite_get_build | Get details for a specific build. | low |
| mcp_buildkite_list_jobs | List all jobs for a specific build. | low |
| mcp_buildkite_list_failed_jobs | List failed jobs for a specific build. | low |
| mcp_buildkite_list_job_spec_failures | List spec failures for a specific job. | low |
| mcp_buildkite_get_job_log | Get the log content for a specific job. | low |
| mcp_buildkite_list_failed_specs | List failed specs from a build URL. | low |
| mcp_buildkite_retry_job | Retry a specific build job. | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›Do I need to run this server manually when using it with Cursor?
No, if you configure it in your ~/.cursor/config/mcp.json file, Cursor will automatically start and stop the server as needed.
›Is an access token always required in the request body?
No, you can provide an access token via the environment variable BUILDKITE_ACCESS_TOKEN, which makes it optional in the individual request bodies.
›What information can I extract from failed jobs?
You can list failed jobs for a build, retrieve specific RSpec failures, or get the logs for a specific job.
Badge
Maintain this server? Add the live badge to your README.