Buildkite

Buildkite

Buildkite MCP lets agents interact with Buildkite Builds, Jobs, Logs, Packages and Test Suites.

624

24 Tools

Signed
Built by Docker
Requires Secrets
Add to Docker Desktop

Version 4.43 or later needs to be installed to add the server automatically

About

Buildkite MCP Server

Buildkite MCP lets agents interact with Buildkite Builds, Jobs, Logs, Packages and Test Suites.

What is an MCP Server?

Characteristics

AttributeDetails
Docker Imagemcp/buildkite
Authorbuildkite
Repositoryhttps://github.com/buildkite/buildkite-mcp-server
Dockerfilehttps://github.com/buildkite/buildkite-mcp-server/blob/main/Dockerfile.local
Docker Image built byDocker Inc.
Docker Scout Health ScoreDocker Scout Health Score
Verify SignatureCOSIGN_REPOSITORY=mcp/signatures cosign verify mcp/buildkite --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
LicenceMIT License

Available Tools (24)

Tools provided by this ServerShort Description
access_tokenGet Access Token
create_buildCreate Build
create_pipelineCreate Pipeline
current_userGet Current User
get_artifactGet Artifact
get_buildGet Build
get_build_test_engine_runsGet Build Test Engine Runs
get_clusterGet Cluster
get_cluster_queueGet Cluster Queue
get_failed_executionsGet Failed Test Executions
get_job_logsGet Job Logs
get_jobsGet Jobs
get_pipelineGet Pipeline
get_testGet Test
get_test_runGet Test Run
list_annotationsList Annotations
list_artifactsArtifact List
list_buildsList Builds
list_cluster_queuesList Cluster Queues
list_clustersList Clusters
list_pipelinesList Pipelines
list_test_runsList Test Runs
update_pipelineUpdate Pipeline
user_token_organizationGet Organization for User Token

Tools Details

Tool: access_token

Get information about the current API access token including its scopes and UUID

Tool: create_build

Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information

ParametersTypeDescription
branchstringThe branch to build
commitstringThe commit SHA to build
messagestringThe commit message for the build
org_slugstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline
environmentarrayoptionalEnvironment variables to set for the build
metadataarrayoptionalMeta-data values to set for the build

Tool: create_pipeline

Set up a new CI/CD pipeline in Buildkite with YAML configuration, repository connection, and cluster assignment

ParametersTypeDescription
cluster_idstringThe ID value of the cluster the pipeline will be associated with
configurationstringThe pipeline configuration in YAML format. Contains the build steps and pipeline settings. If not provided, a basic configuration will be used
namestringThe name of the pipeline
org_slugstringThe organization slug for the owner of the pipeline. This is used to determine where to create the pipeline
repository_urlstringThe Git repository URL to use for the pipeline
cancel_running_branch_buildsbooleanoptionalCancel running builds when new builds are created on the same branch
default_branchstringoptionalThe default branch for builds and metrics filtering
descriptionstringoptionalThe description of the pipeline
skip_queued_branch_buildsbooleanoptionalSkip intermediate builds when new builds are created on the same branch
tagsarrayoptionalTags to apply to the pipeline. These can be used for filtering and organization

Tool: current_user

Get details about the user account that owns the API token, including name, email, avatar, and account creation date

Tool: get_artifact

Get detailed information about a specific artifact including its metadata, file size, SHA-1 hash, and download URL

ParametersTypeDescription
urlstringThe URL of the artifact to get

This tool is read-only. It does not modify its environment.


Tool: get_build

Get detailed information about a specific build including its jobs, timing, and execution details

ParametersTypeDescription
build_numberstringThe number of the build
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline

This tool is read-only. It does not modify its environment.


Tool: get_build_test_engine_runs

Get test engine runs data for a specific build in Buildkite. This can be used to look up Test Runs.

ParametersTypeDescription
build_numberstringThe number of the build
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline

This tool is read-only. It does not modify its environment.


Tool: get_cluster

Get detailed information about a specific cluster including its name, description, default queue, and configuration

ParametersTypeDescription
cluster_idstringThe id of the cluster
orgstringThe organization slug for the owner of the pipeline

This tool is read-only. It does not modify its environment.


Tool: get_cluster_queue

Get detailed information about a specific queue including its key, description, dispatch status, and hosted agent configuration

ParametersTypeDescription
cluster_idstringThe id of the cluster
orgstringThe organization slug for the owner of the pipeline
queue_idstringThe id of the queue

This tool is read-only. It does not modify its environment.


Tool: get_failed_executions

Get failed test executions for a specific test run in Buildkite Test Engine. Optionally get the expanded failure details such as full error messages and stack traces.

ParametersTypeDescription
orgstringThe organization slug for the owner of the test suite
run_idstringThe ID of the test run
test_suite_slugstringThe slug of the test suite the run belongs to
include_failure_expandedbooleanoptionalInclude the expanded failure details such as full error messages and stack traces. This can be used to explain and diganose the cause of test failures.
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: get_job_logs

Get the log output and metadata for a specific job, including content, size, and header timestamps. Automatically saves to file for large logs to avoid token limits.

ParametersTypeDescription
build_numberstringThe build number
job_uuidstringThe UUID of the job
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline

Tool: get_jobs

Get all jobs for a specific build including their state, timing, commands, and execution details

ParametersTypeDescription
build_numberstringThe number of the build
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline
include_agentbooleanoptionalInclude detailed agent information in the response. When false (default), only agent ID is included to reduce response size.
job_statestringoptionalFilter jobs by state. Supports actual states (scheduled, running, passed, failed, canceled, skipped, etc.)
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 50)

This tool is read-only. It does not modify its environment.


Tool: get_pipeline

Get detailed information about a specific pipeline including its configuration, steps, environment variables, and build statistics

ParametersTypeDescription
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline

This tool is read-only. It does not modify its environment.


Tool: get_test

Get a specific test in Buildkite Test Engine. This provides additional metadata for failed test executions

ParametersTypeDescription
orgstringThe organization slug for the owner of the test suite
test_idstringThe ID of the test
test_suite_slugstringThe slug of the test suite

This tool is read-only. It does not modify its environment.


Tool: get_test_run

Get a specific test run in Buildkite Test Engine

ParametersTypeDescription
orgstringThe organization slug for the owner of the test suite
run_idstringThe ID of the test run
test_suite_slugstringThe slug of the test suite

This tool is read-only. It does not modify its environment.


Tool: list_annotations

List all annotations for a build, including their context, style (success/info/warning/error), rendered HTML content, and creation timestamps

ParametersTypeDescription
build_numberstringThe build number
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: list_artifacts

List all artifacts for a build across all jobs, including file details, paths, sizes, MIME types, and download URLs

ParametersTypeDescription
build_numberstringThe build number
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline

This tool is read-only. It does not modify its environment.


Tool: list_builds

List all builds for a pipeline with their status, commit information, and metadata

ParametersTypeDescription
orgstringThe organization slug for the owner of the pipeline
pipeline_slugstringThe slug of the pipeline
branchstringoptionalFilter builds by git branch name
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: list_cluster_queues

List all queues in a cluster with their keys, descriptions, dispatch status, and agent configuration

ParametersTypeDescription
cluster_idstringThe id of the cluster
orgstringThe organization slug for the owner of the pipeline
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: list_clusters

List all clusters in an organization with their names, descriptions, default queues, and creation details

ParametersTypeDescription
orgstringThe organization slug for the owner of the pipeline
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: list_pipelines

List all pipelines in an organization with their basic details, build counts, and current status

ParametersTypeDescription
orgstringThe organization slug for the owner of the pipeline
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: list_test_runs

List all test runs for a test suite in Buildkite Test Engine

ParametersTypeDescription
orgstringThe organization slug for the owner of the test suite
test_suite_slugstringThe slug of the test suite
pagenumberoptionalPage number for pagination (min 1)
perPagenumberoptionalResults per page for pagination (min 1, max 100)

This tool is read-only. It does not modify its environment.


Tool: update_pipeline

Modify an existing Buildkite pipeline's configuration, repository, settings, or metadata

ParametersTypeDescription
org_slugstringThe organization slug for the owner of the pipeline. This is used to determine where to update the pipeline
pipeline_slugstringThe slug of the pipeline to update
cancel_running_branch_buildsbooleanoptionalCancel running builds when new builds are created on the same branch
cluster_idstringoptionalThe ID value of the cluster the pipeline will be associated with
configurationstringoptionalThe pipeline configuration in YAML format. Contains the build steps and pipeline settings. If not provided, the existing configuration will be used
default_branchstringoptionalThe default branch for builds and metrics filtering
descriptionstringoptionalThe description of the pipeline
namestringoptionalThe name of the pipeline
repository_urlstringoptionalThe Git repository URL to use for the pipeline
skip_queued_branch_buildsbooleanoptionalSkip intermediate builds when new builds are created on the same branch
tagsarrayoptionalTags to apply to the pipeline. These can be used for filtering and organization

Tool: user_token_organization

Get the organization associated with the user token used for this request

Use this MCP Server

{
  "mcpServers": {
    "buildkite": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BUILDKITE_API_TOKEN",
        "mcp/buildkite"
      ],
      "env": {
        "BUILDKITE_API_TOKEN": "bkua_xxxxx"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?

Manual installation

You can install the MCP server using:

Installation for

Related servers