mcp/buildkite-mcp-server pulls statistics

Buildkite MCP Server

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

What is an MCP Server?

Characteristics

Attribute|Details| |-|-| Docker Image|mcp/buildkite-mcp-server Author|buildkite Repository|https://github.com/buildkite/buildkite-mcp-server Dockerfile|https://github.com/buildkite/buildkite-mcp-server/blob/main/Dockerfile.local Docker Image built by|Docker Inc. Docker Scout Health Score| Verify Signature|COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/buildkite-mcp-server --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub Licence|MIT License

Available Tools (24)

Tools provided by this Server|Short Description -|- access_token|Get Access Token| create_build|Create Build| create_pipeline|Create Pipeline| current_user|Get Current User| get_artifact|Get Artifact| get_build|Get Build| get_build_test_engine_runs|Get Build Test Engine Runs| get_cluster|Get Cluster| get_cluster_queue|Get Cluster Queue| get_failed_executions|Get Failed Test Executions| get_job_logs|Get Job Logs| get_jobs|Get Jobs| get_pipeline|Get Pipeline| get_test|Get Test| get_test_run|Get Test Run| list_annotations|List Annotations| list_artifacts|List Artifacts| list_builds|List Builds| list_cluster_queues|List Cluster Queues| list_clusters|List Clusters| list_pipelines|List Pipelines| list_test_runs|List Test Runs| update_pipeline|Update Pipeline| user_token_organization|Get 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 Parameters|Type|Description -|-|- branch|string|The branch to build commit|string|The commit SHA to build message|string|The commit message for the build org_slug|string|The organization slug for the owner of the pipeline pipeline_slug|string|The slug of the pipeline environment|array *optional*|Environment variables to set for the build metadata|array *optional*|Environment variables 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 Parameters|Type|Description -|-|- cluster_id|string|The ID value of the cluster the pipeline will be associated with configuration|string|The pipeline configuration in YAML format. Contains the build steps and pipeline settings. If not provided, a basic configuration will be used name|string|The name of the pipeline org_slug|string|The organization slug for the owner of the pipeline. This is used to determine where to create the pipeline repository_url|string|The Git repository URL to use for the pipeline cancel_running_branch_builds|boolean *optional*|Cancel running builds when new builds are created on the same branch default_branch|string *optional*|The default branch for builds and metrics filtering description|string *optional*|The description of the pipeline skip_queued_branch_builds|boolean *optional*|Skip intermediate builds when new builds are created on the same branch tags|array *optional*|Tags 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 Parameters|Type|Description -|-|- url|string|The 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 Parameters|Type|Description -|-|- build_number|string|The number of the build org|string|The organization slug for the owner of the pipeline pipeline_slug|string|The 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. Parameters|Type|Description -|-|- build_number|string|The number of the build org|string|The organization slug for the owner of the pipeline pipeline_slug|string|The 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 Parameters|Type|Description -|-|- cluster_id|string|The id of the cluster org|string|The 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 Parameters|Type|Description -|-|- cluster_id|string|The id of the cluster org|string|The organization slug for the owner of the pipeline queue_id|string|The 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. Parameters|Type|Description -|-|- org|string|The organization slug for the owner of the test suite run_id|string|The ID of the test run test_suite_slug|string|The slug of the test suite the run belongs to include_failure_expanded|boolean *optional*|Include 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. page|number *optional*|Page number for pagination (min 1) perPage|number *optional*|Results per page for pagination (min 1, max 100)…

Description from the Docker Hub listing.