v1.19.0

Buildkite MCP server v1.19.0 adds per-build Test Engine results (list_tests_for_build), dynamic pipeline upload inspection (list_step_uploads, get_step_upload), and job state counts in build failure summaries — so AI agents can debug CI/CD builds with fewer API calls.

What's Changed

Features

• feat: add list_tests_for_build MCP tool by @meghan-kradolfer in #369
• Add list_step_uploads and get_step_upload tools by @nethsix in #364
• feat: propagate job_state_counts into get_build_failure_summary by @nethsix in #368

Dependencies

• chore(deps): bump go-buildkite to v5.14.0 by @nethsix in #368
• fix(deps): update module github.com/stretchr/testify to v1.12.0 by @renovate[bot] in #366
• chore(deps): update dependency go to v1.26.6 by @renovate[bot] in #365

Tool Changes

New tool: list_tests_for_build

• Lists Buildkite Test Engine tests and their execution metrics for a single build, looked up by build UUID (the build ID, not the pipeline build number).
• Supports the same filters as list_tests — labels, branch, owners, test state, and execution tags — plus metric sorting (duration_avg, duration_sum, duration_min, duration_max, reliability) and pagination.
• Lets agents answer "which tests ran, failed, or were flaky in this build?" without aggregating across a whole suite time window.

New tools: list_step_uploads and get_step_upload

• list_step_uploads lists the dynamic pipeline uploads (buildkite-agent pipeline upload) a build received, newest first. Each item includes the upload state, the uploading job (source_job_id), created_jobs_count, and rejection details, with optional filtering by source job and cursor-based pagination.
• get_step_upload fetches a single upload including its pipeline definition rendered as YAML (definition_yaml). Definitions over the API's render limit are flagged with definition_yaml_omitted: true and their size in definition_bytes instead of being returned.
• Both tools work while the build is within its maximum lifetime (roughly 30 days); older builds return 410 Gone.
• get_build now points agents at list_step_uploads to see the dynamic pipeline configuration a build received.

Changes to get_build_failure_summary:

• Now includes job_state_counts, a tally of every job in the build by state. When present, it confirms whether the returned problem jobs are the build's only problems — no follow-up list_jobs call needed. Omitted when the API does not return it.

Full Changelog: v1.18.0...v1.19.0