Buildkite MCP Server
by Drew-Goddyn
A microservice for retrieving information from Buildkite via Model Context Protocol (MCP). It allows you to query Buildkite data such as organizations, pipelines, builds, and jobs.
Last updated: N/A
What is Buildkite MCP Server?
The Buildkite MCP Server is a Node.js application that acts as a bridge between Buildkite and applications using the Model Context Protocol (MCP). It provides a standardized way to access Buildkite data through a set of defined endpoints.
How to use Buildkite MCP Server?
- Clone the repository. 2. Run
npm install. 3. Set theBUILDKITE_ACCESS_TOKENenvironment variable with your Buildkite API token. 4. Start the server withnode index.js. Alternatively, configure it within Cursor'smcp.jsonfile for automatic start and stop.
Key features of Buildkite MCP Server
Retrieves Buildkite organization information
Lists pipelines within an organization
Lists builds for a pipeline
Retrieves details for a specific build
Lists jobs (including failed jobs) for a build
Retrieves job logs
Lists failed specs from a build URL
Retries a job
Lists pipeline build failures
Use cases of Buildkite MCP Server
Integrating Buildkite data into IDEs like Cursor
Automating analysis of build failures
Creating custom dashboards for Buildkite metrics
Triggering actions based on build status
Enabling advanced code intelligence features
FAQ from Buildkite MCP Server
What is the Model Context Protocol (MCP)?
What is the Model Context Protocol (MCP)?
MCP is a protocol that allows applications to access data from various sources in a standardized way.
How do I get a Buildkite API token?
How do I get a Buildkite API token?
You can generate an API token with read access from your Buildkite organization settings.
What if I don't want to run the server manually?
What if I don't want to run the server manually?
You can configure the server within Cursor's mcp.json file, and Cursor will automatically start and stop it as needed.
What environment variables are required?
What environment variables are required?
The BUILDKITE_ACCESS_TOKEN environment variable is required. The PORT variable is optional and defaults to 63330.
What kind of error handling is implemented?
What kind of error handling is implemented?
The server returns standard HTTP status codes such as 400, 401, 404, and 500 to indicate different types of errors.