Buildkite
Inspect Buildkite CI/CD — pipelines, builds, jobs, and logs. Sign in with Buildkite to connect.
What Buildkite exposes.
Every tool below is one this server advertised the last time Omniio refreshed it, under the buildkite__ namespace. Your agent never loads them all — it searches, and gets the few that match.
buildkite__access_token1 argument · 1 required
Get information about the current API access token including its scopes and UUID
Required
telemetrybuildkite__cancel_build4 arguments · 4 required
Cancel a running build on a Buildkite pipeline
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__create_annotation11 arguments · 5 required
Create an annotation on a build or specific job. Use scope='build' (default) or scope='job' with job_id
Required
telemetryorg_slugpipeline_slugbuild_numberbodybuildkite__create_build9 arguments · 6 required
Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information
Required
telemetryorg_slugpipeline_slugcommitbranchmessagebuildkite__create_cluster6 arguments · 3 required
Create a new cluster in an organization
Required
telemetryorg_slugnamebuildkite__create_cluster_queue5 arguments · 4 required
Create a new queue in a cluster
Required
telemetryorg_slugcluster_idkeybuildkite__create_cluster_secret7 arguments · 5 required
Create cluster secret
Required
telemetryorg_slugcluster_idkeyvaluebuildkite__create_pipeline13 arguments · 6 required
Set up a new CI/CD pipeline in Buildkite with YAML configuration, repository connection, and cluster assignment
Required
telemetryorg_slugnamerepository_urlcluster_idconfigurationbuildkite__create_pipeline_schedule10 arguments · 4 required
Create a new pipeline schedule that triggers builds on a cron-driven interval
Required
telemetryorg_slugpipeline_slugcronlinebuildkite__current_user1 argument · 1 required
Get details about the user account that owns the API token, including name, email, avatar, and account creation date
Required
telemetrybuildkite__get_agent4 arguments · 3 required
Get detailed information about a specific agent including its connection state, host details, current job, metadata, and pause status
Required
telemetryorg_slugagent_idbuildkite__get_artifact6 arguments · 6 required
Get a specific artifact by organization, pipeline, build, job, and artifact identifiers. Text artifacts under 64 KiB are returned inline in `content`; larger or binary artifacts return metadata plus a short-lived `download_url`. When `download_url_auth` is "none" the URL is presigned (a buildkiteartifacts.com S3 link) — fetch it with a plain GET and NO Authorization header. It expires after `download_url_expires_in_seconds`; if it has expired, call this tool again for a fresh URL.
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idartifact_idbuildkite__get_build4 arguments · 4 required
Get a single build with lightweight annotation summaries. Annotation bodies and jobs are not included — use list_annotations to read annotations, list_jobs or get_job for job detail, and list_step_uploads to see the dynamic pipeline configuration the build received via `buildkite-agent pipeline upload`
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__get_build_failure_summary15 arguments · 4 required
Diagnose a Buildkite build failure in one call. Returns build.state, build.job_state_counts tallying every job in the build by state (when present, use it to confirm the returned problem jobs are the build's only problems without calling list_jobs), terminal problem jobs, downstream failed or broken jobs, promised failures from running jobs, and size-bounded diagnostic content from logs, annotations, and failed Test Engine executions. Annotation content is in the body_html field; there is no body field. Start with this tool before calling individual job, log, annotation, or test tools.
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__get_build_test_engine_runs4 arguments · 4 required
Get test engine runs data for a specific build in Buildkite. This can be used to look up Test Runs.
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__get_cluster3 arguments · 3 required
Get detailed information about a specific cluster including its name, description, default queue, and configuration
Required
telemetryorg_slugcluster_idbuildkite__get_cluster_queue4 arguments · 4 required
Get detailed information about a specific queue including its key, description, dispatch status, and hosted agent configuration
Required
telemetryorg_slugcluster_idqueue_idbuildkite__get_cluster_secret4 arguments · 4 required
Get cluster secret information
Required
telemetryorg_slugcluster_idsecret_idbuildkite__get_failed_executions7 arguments · 4 required
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.
Required
telemetryorg_slugtest_suite_slugrun_idbuildkite__get_job6 arguments · 3 required
Get a single job by its UUID. Provide 'pipeline_slug' and 'build_number' for a build-scoped lookup, or omit both to look the job up by organization and job ID alone
Required
telemetryorg_slugjob_idbuildkite__get_job_env5 arguments · 5 required
Get the environment variables for a specific job in a Buildkite build
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idbuildkite__get_pipeline4 arguments · 3 required
Get detailed information about a specific pipeline including its configuration, steps, environment variables, and build statistics
Required
telemetryorg_slugpipeline_slugbuildkite__get_pipeline_schedule4 arguments · 4 required
Get detailed information about a single pipeline schedule including its cron expression, target branch, environment variables, enabled state, last failure, and next build time
Required
telemetryorg_slugpipeline_slugschedule_idbuildkite__get_step_upload5 arguments · 5 required
Get a single dynamic pipeline upload including its pipeline definition rendered as YAML (definition_yaml). Definitions over the API's render limit are omitted: definition_yaml is omitted, definition_yaml_omitted is true and definition_bytes reports the size. Only available while the build is within its maximum lifetime (~30 days); older builds return 410 Gone
Required
telemetryorg_slugpipeline_slugbuild_numberupload_uuidbuildkite__get_test7 arguments · 4 required
Get a specific test in Buildkite Test Engine, including execution metrics aggregated over a selected time window. This provides additional metadata for failed test executions.
Required
telemetryorg_slugtest_suite_slugtest_idbuildkite__get_test_run4 arguments · 4 required
Get a specific test run in Buildkite Test Engine
Required
telemetryorg_slugtest_suite_slugrun_idbuildkite__list_agents9 arguments · 2 required
List agents in an organization with their connection state, host details, version, current job, and pause status
Required
telemetryorg_slugbuildkite__list_annotations8 arguments · 4 required
List annotations for a build or a specific job. Use scope='build' (default) or scope='job' with job_id. Annotation content is in the body_html field; there is no body field
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__list_artifacts_for_build6 arguments · 4 required
List all artifacts for a build across all jobs, including filenames, paths, sizes, and MIME types. Output can be large for big builds — use per_page and paginate. To fetch an artifact's contents or a download URL, call get_artifact with that artifact's id and job_id.
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__list_artifacts_for_job7 arguments · 5 required
List all artifacts for an individual job, including filenames, paths, sizes, and MIME types. To fetch an artifact's contents or a download URL, call get_artifact with that artifact's id and job_id.
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idbuildkite__list_builds9 arguments · 2 required
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
Required
telemetryorg_slugbuildkite__list_cluster_queues5 arguments · 3 required
List all queues in a cluster with their keys, descriptions, dispatch status, and agent configuration
Required
telemetryorg_slugcluster_idbuildkite__list_cluster_secrets5 arguments · 3 required
List cluster secrets
Required
telemetryorg_slugcluster_idbuildkite__list_clusters4 arguments · 2 required
List all clusters in an organization with their names, descriptions, default queues, and creation details
Required
telemetryorg_slugbuildkite__list_jobs13 arguments · 4 required
List jobs for a Buildkite build, returning an actionable summary by default. For CI failure diagnosis, use state='failed,broken' to avoid returning successful jobs. Use detail_level='detailed' for execution metadata or 'full' for the existing full MCP job response. Returns 'items' and cursor pagination 'links'
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__list_pipeline_schedules5 arguments · 3 required
List the pipeline schedules for a pipeline, including cron expression, target branch, environment variables, enabled state, and next scheduled build time
Required
telemetryorg_slugpipeline_slugbuildkite__list_pipelines7 arguments · 2 required
List all pipelines in an organization with their basic details, build counts, and current status
Required
telemetryorg_slugbuildkite__list_skills2 arguments · 1 required
List available skill guides that document usage patterns, pitfalls, and workflows for Buildkite MCP tools
Required
telemetrybuildkite__list_step_uploads8 arguments · 4 required
List the dynamic pipeline uploads (`buildkite-agent pipeline upload`) a build received, newest first, without their definitions. Each item includes state, the uploading job (source_job_id), created_jobs_count (omitted until applied, 0 when applied but no jobs were created), and rejection details. Use get_step_upload to read an upload's pipeline definition. Only available while the build is within its maximum lifetime (~30 days); older builds return 410 Gone
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__list_test_runs5 arguments · 3 required
List all test runs for a test suite in Buildkite Test Engine
Required
telemetryorg_slugtest_suite_slugbuildkite__list_test_suites_for_pipeline5 arguments · 3 required
List the Buildkite Test Engine suites that have recorded at least one run attributed to a pipeline, ordered by creation time. Use this to find the test_suite_slug needed by the other Test Engine tools.
Required
telemetryorg_slugpipeline_slugbuildkite__list_tests16 arguments · 3 required
List tests in a Buildkite Test Engine suite with execution metrics aggregated over a selected time window. Supports filtering, metric sorting, and pagination.
Required
telemetryorg_slugtest_suite_slugbuildkite__list_tests_for_build12 arguments · 3 required
List tests and their execution metrics for a Buildkite build. Requires the build UUID (the build ID, not the pipeline build number) and supports filtering, metric sorting, and pagination.
Required
telemetryorg_slugbuild_uuidbuildkite__load_skill2 arguments · 2 required
Load the full content of a skill guide by name
Required
telemetryskill_namebuildkite__pause_cluster_queue_dispatch5 arguments · 4 required
Pause dispatch on a cluster queue, preventing new jobs from being dispatched to agents
Required
telemetryorg_slugcluster_idqueue_idbuildkite__read_logs9 arguments · 5 required
Read log entries from the file, optionally starting from a specific row number. ALWAYS use 'limit' parameter to avoid excessive tokens. For recent failures, use 'tail_logs' instead. Recommended limits: investigation (100-500), exploration (use seek + small limits). The json format: {ts: timestamp_ms, c: content, rn: row_number}.
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idbuildkite__rebuild_build4 arguments · 4 required
Rebuild/retry an entire build on a Buildkite pipeline
Required
telemetryorg_slugpipeline_slugbuild_numberbuildkite__resume_cluster_queue_dispatch4 arguments · 4 required
Resume dispatch on a paused cluster queue, allowing jobs to be dispatched to agents again
Required
telemetryorg_slugcluster_idqueue_idbuildkite__retry_job5 arguments · 5 required
Retry a specific failed or timed out job in a Buildkite build
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idbuildkite__search_logs16 arguments · 6 required
Search log entries using regex patterns with optional context lines. For recent failures, try 'tail_logs' first, then use search_logs with patterns like 'error|failed|exception' and limit: 10-20. The json format: {ts: timestamp_ms, c: content, rn: row_number}.
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idpatternbuildkite__tail_logs8 arguments · 5 required
Show the last N entries from the log file. RECOMMENDED for failure diagnosis - most build failures appear in the final log entries. More token-efficient than read_logs for recent issues. The json format: {ts: timestamp_ms, c: content, rn: row_number}.
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idbuildkite__unblock_job6 arguments · 5 required
Unblock a blocked job in a Buildkite build to allow it to continue execution
Required
telemetryorg_slugpipeline_slugbuild_numberjob_idbuildkite__update_cluster8 arguments · 3 required
Update an existing cluster's name, description, emoji, color, or default queue
Required
telemetryorg_slugcluster_idbuildkite__update_cluster_queue6 arguments · 4 required
Update an existing cluster queue's description or retry agent affinity
Required
telemetryorg_slugcluster_idqueue_idbuildkite__update_pipeline12 arguments · 3 required
Modify an existing Buildkite pipeline's configuration, repository, settings, or metadata
Required
telemetryorg_slugpipeline_slugbuildkite__update_pipeline_schedule11 arguments · 4 required
Modify an existing pipeline schedule's cron expression, branch, environment variables, or enabled state
Required
telemetryorg_slugpipeline_slugschedule_idbuildkite__user_token_organization1 argument · 1 required
Get the organization associated with the user token used for this request
Required
telemetrybuildkite__wait_for_build4 arguments · 4 required
Wait for a build to reach a terminal state (passed, failed, canceled, skipped, not_run, or blocked on a block step), polling for up to 45 seconds. Returns finished=true along with the build once it settles. If the build is still in progress when the window closes it returns finished=false and the current state only, with no build detail — call this tool again to keep waiting. Judge a long build by build_elapsed_seconds, which counts from the build's own start time and does not reset between calls; waited_seconds covers only the latest call. Do not wait indefinitely: after roughly ten consecutive calls, stop and report the build as still running with its elapsed time rather than continuing to poll. Jobs and annotation bodies are never included — use list_jobs or get_job for job detail, and list_annotations to read annotations
Required
telemetryorg_slugpipeline_slugbuild_number
Three steps, and the last one is not yours.
Point a client at Omniio
One URL, authorized once by your client. If you already use Omniio, this step is done.
Switch Buildkite on
Authorize it from your library; the grant is yours and stays yours.
Ask for what you need
The agent searches, reads the one schema it picked, and runs it. You do not name the tool.
claude mcp add --transport http omniio https://mcp.omniio.dev
