Buildkite MCP, Buildkite's official MCP server

• Explains why a build failed in one step

  Diagnoses a failed build in one call, with the build state, a count of jobs by state and details of the problem jobs.

  Try: “Why did build 1234 on the web pipeline fail?”

  Network · get_build_failure_summary

• Lists recent builds, newest first

  Lists builds for one pipeline, or across all pipelines in an organization, with light details.

  Try: “Show the last 10 builds on main for the web pipeline.”

  Network · list_builds

• Shows one build

  Returns a single build with short annotation summaries.

  Try: “Show me the details of build 1234.”

  Network · get_build

• Compares a build with an earlier one

  Compares step results, retries and timing between builds of one pipeline. Picks an earlier build in the same pipeline as the baseline.

  Try: “What changed since this build last passed on main?”

  Network · compare_builds

• Waits until a build finishes

  Polls a build until it passes, fails, is canceled or is blocked.

  Try: “Wait for build 1234 to finish and tell me the result.”

  Network · wait_for_build

• Lists the jobs in a build

  Lists jobs for a build with a short summary, and can filter to failed or timed-out jobs.

  Try: “List the failed jobs in build 1234.”

  Network · list_jobs

• Shows one job

  Returns a single job by its ID.

  Try: “Show me details of the failed test job.”

  Network · get_job

• Shows a job's environment variables

  Returns the environment variables set for a job. This can expose values you would rather keep private.

  Try: “Show the environment variables of the deploy job.”

  Network · get_job_env

• Shows the last lines of a job log

  Returns the last entries of a job log, which is where most failures show up.

  Try: “Show the last 50 lines of the failed job's log.”

  Network · tail_logs

• Searches a job log with a pattern

  Searches log entries with a regular expression and optional surrounding lines.

  Try: “Search that log for "ECONNRESET" with 5 lines of context.”

  Network · search_logs

• Reads a job log from a chosen row

  Reads log entries, optionally starting at a row number, with a limit.

  Try: “Read the first 100 lines of that job's log.”

  Network · read_logs

• Lists the pipelines in an organization

  Lists pipelines with basic details, build counts and status.

  Try: “List all pipelines in my organization.”

  Network · list_pipelines

• Shows one pipeline's setup

  Returns a pipeline's configuration, steps, environment variables and build statistics.

  Try: “Show me how the deploy pipeline is configured.”

  Network · get_pipeline

• Checks pipeline YAML against the schema

  Validates pipeline YAML against Buildkite's schema without calling the API.

  Try: “Validate this pipeline.yml.”

  Read · validate_pipeline

• Lists files a build produced

  Lists artifacts across all jobs of a build with names, paths, sizes and types.

  Try: “What artifacts did build 1234 produce?”

  Network · list_artifacts_for_build

• Reads one build artifact

  Returns an artifact. Text files under 64 KiB come back inline.

  Try: “Open the coverage summary artifact from that build.”

  Network · get_artifact

• Lists notes attached to a build or job

  Lists annotations for a build or a single job.

  Try: “Show the annotations on build 1234.”

  Network · list_annotations

• Lists your build agents

  Lists agents with connection state, host details, version, current job and pause status.

  Try: “Which agents are offline right now?”

  Network · list_agents

• Lists your clusters

  Lists clusters with names, descriptions and default queues.

  Try: “List my clusters.”

  Network · list_clusters

• Lists the queues in a cluster

  Lists queues with keys, dispatch status and agent configuration.

  Try: “Which queues in the main cluster are paused?”

  Network · list_cluster_queues

• Lists tests in a Test Engine suite

  Lists tests with execution metrics over a time window, with filtering.

  Try: “Which tests in the unit suite were slowest this week?”

  Network · list_tests

• Shows one Test Engine run

  Returns a specific test run in Test Engine.

  Try: “Show me the latest test run for the unit suite.”

  Network · get_test_run

• Lists the failed tests in a test run

  Returns failed test executions for a run, with expanded failure details if you ask.

  Try: “Which tests failed in that run, and why?”

  Network · get_failed_executions

• Finds the test suites a pipeline reports to

  Lists Test Engine suites with recorded runs from a pipeline.

  Try: “Which test suites does the web pipeline report to?”

  Network · list_test_suites_for_pipeline

• Shows who the token belongs to

  Returns the name, email and account details of the token's owner.

  Try: “Which Buildkite user am I connected as?”

  Network · current_user

• Shows what the current token can do

  Returns the current API token's scopes and ID.

  Try: “What permissions does my token have?”

  Network · access_token

• Starts a new build

  Triggers a build on a pipeline for a commit and branch, with optional environment variables and metadata. Pipelines can run deploy steps.

  Try: “Start a build of main on the web pipeline.”

  Write · create_build

• Re-runs a whole build

  Rebuilds an entire build on a pipeline.

  Try: “Rebuild build 1234.”

  Write · rebuild_build

• Retries one failed job

  Retries a specific failed or timed-out job.

  Try: “Retry the failed lint job in build 1234.”

  Write · retry_job

• Retries failed jobs that are safe to retry

  Retries only failures it considers safe, and reports every job it retried or skipped with a reason. Has a dry-run option.

  Try: “Do a dry run of retrying the failed jobs in build 1234.”

  Write · retry_failed_jobs

• Cancels a running build

  Cancels a running build on a pipeline.

  Try: “Cancel build 1234.”

  Write · cancel_build

• Cancels one job

  Cancels a single command job without canceling the rest of the build.

  Try: “Cancel the stuck integration job.”

  Write · cancel_job

• Approves a blocked step

  Unblocks a job that is waiting on a block step so the build continues. A block step is often a deploy approval.

  Try: “Unblock the production deploy step.”

  Write · unblock_job

• Adds a note to a build or job

  Creates an annotation on a build or a job.

  Try: “Add an annotation to build 1234 saying the retry was approved.”

  Write · create_annotation

• Sets up a new pipeline

  Creates a pipeline from YAML or an approved template, with a repository connection and cluster.

  Try: “Create a pipeline for the docs repo from this YAML.”

  Write · create_pipeline

• Changes a pipeline's settings

  Modifies a pipeline's configuration, repository, settings or metadata.

  Try: “Change the default branch of the web pipeline to main.”

  Write · update_pipeline

• Schedules builds on a cron timer

  Creates a schedule that triggers builds on a cron interval.

  Try: “Schedule a nightly build of main at 2am.”

  Write · create_pipeline_schedule

• Changes a build schedule

  Modifies a schedule's cron expression, branch, environment variables or enabled state.

  Try: “Disable the nightly schedule.”

  Write · update_pipeline_schedule

• Creates a cluster

  Creates a new cluster in an organization.

  Try: “Create a cluster called staging-agents.”

  Write · create_cluster

• Stores a secret in a cluster

  Creates a secret in a cluster.

  Try: “Create a cluster secret named DEPLOY_KEY.”

  Write · create_cluster_secret

• Stops a queue from sending out jobs

  Pauses dispatch on a queue so no new jobs go to its agents.

  Try: “Pause the deploy queue.”

  Write · pause_cluster_queue_dispatch

• Lets a paused queue send out jobs again

  Resumes dispatch on a paused queue.

  Try: “Resume the deploy queue.”

  Write · resume_cluster_queue_dispatch

• Used by the assistant behind the scenes

  Loads a usage guide for the tools

  Loads a built-in guide that explains patterns and pitfalls for using the Buildkite tools.

  Try: “Load the Buildkite skill guide for fixing failed builds.”

  Read · load_skill

Watch out for

• It can start and unblock builds that deploy

  Starting a build or approving a block step can run pipeline commands, including deployments. Keep approval prompts on for write actions in your AI tool. buildkite.com

• It can read job environment variables and logs

  Logs and job settings can contain secrets that your pipeline prints or sets. Everything it reads goes to your AI provider. github.com

• It can create secrets and change queues

  Tools can store cluster secrets, pause a queue and change pipeline settings. The read-only address removes all of them. github.com

• Read-only is not a sandbox

  Buildkite notes that an agent with shell access and a signed-in Buildkite CLI can still make changes with the CLI. buildkite.com

Security advisories