Buildkite
Expose pipelines, builds, jobs, and Test Engine data to AI tools.
Buildkite
Expose pipelines, builds, jobs, and Test Engine data to AI tools. With Lunar.dev MCPX, the MCP Gateway for secure and governed tool access, you connect the Buildkite MCP server to Claude, ChatGPT, Cursor, and any MCP client through one gateway that routes, authenticates, and governs every Buildkite tool call against your policies.
Why MCPX
MCPX is Lunar.dev's MCP Gateway. It sits between your AI agents and your MCP servers as a single gateway for every tool call, routing, authenticating, and governing traffic against your policies. Connect Buildkite once and govern it everywhere: role-based access per agent with on-behalf-of attribution, real-time visibility, and an immutable audit trail of who did what, all deployable inside your own VPC.
Tools content
- access_token · Read-only
Get information about the current API access token including its scopes and UUID - list_agents · Read-only
List agents in an organization with their connection state, host details, version, current job, and pause status - get_agent · Read-only
Get detailed information about a specific agent including its connection state, host details, current job, metadata, and pause status - list_annotations · Read-only
List annotations for a build or a specific job. Use scope='build' (default) or scope='job' with job_id - create_annotation · Write
Create an annotation on a build or specific job. Use scope='build' (default) or scope='job' with job_id - list_artifacts_for_build · Read-only
List all artifacts for a build across all jobs, including file details, paths, sizes, MIME types, and download URLs - list_artifacts_for_job · Read-only
List all artifacts for an individual job, including file details, paths, sizes, MIME types, and download URLs - get_artifact · Read-only
Download a specific artifact's content, identified by its organization, pipeline, build, job, and artifact identifiers. The content is returned base64-encoded - list_builds · Read-only
List builds for a pipeline or across all pipelines in an organization, returning a lightweight summary of each build. When pipeline_slug is omitted, lists builds across all pipelines in the organization. Jobs are not included — use list_jobs or get_job for job detail - get_build_test_engine_runs · Read-only
Get test engine runs data for a specific build in Buildkite. This can be used to look up Test Runs. - get_build · Read-only
Get a single build. Jobs are not included — use list_jobs or get_job for job detail - create_build · Write
Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information - cancel_build · Write
Cancel a running build on a Buildkite pipeline - rebuild_build · Write
Rebuild/retry an entire build on a Buildkite pipeline - list_cluster_queues · Read-only
List all queues in a cluster with their keys, descriptions, dispatch status, and agent configuration - get_cluster_queue · Read-only
Get detailed information about a specific queue including its key, description, dispatch status, and hosted agent configuration - create_cluster_queue · Write
Create a new queue in a cluster - update_cluster_queue · Write
Update an existing cluster queue's description or retry agent affinity - pause_cluster_queue_dispatch · Write
Pause dispatch on a cluster queue, preventing new jobs from being dispatched to agents - resume_cluster_queue_dispatch · Write
Resume dispatch on a paused cluster queue, allowing jobs to be dispatched to agents again
Frequently asked questions
What is the Buildkite MCP server?
Expose pipelines, builds, jobs, and Test Engine data to AI tools. Through Lunar.dev MCPX, Buildkite connects to any MCP-compatible AI client behind a single governed gateway.
How do I connect Buildkite to MCPX?
Add the Buildkite server in the MCPX control plane or your app.yaml, then point your AI client at your MCPX gateway. MCPX handles Token and routes every Buildkite call through the gateway.
Is the Buildkite MCP server official?
Yes. Buildkite is an official, vendor-published MCP server, and MCPX governs it like any other server in your catalog.
What authentication does Buildkite use with MCPX?
Buildkite uses Token. MCPX enforces authentication at the gateway with token-based auth, OAuth, and role-based profiles, so you control which agents can invoke it.
How many tools does Buildkite expose in MCPX?
Buildkite exposes 44 tools. In MCPX you can enable or disable each tool per agent for least-privilege access.
