buildkite/buildkite-mcp-server

v1.4.0 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 15h MCP Developer Tools

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

buildkite mcp-server

Affected surfaces

breaking_upgrade

ReleasePort's take

Moderate signal

editorial:auto 11h

The `get_artifact` API no longer accepts a `url` argument; instead it requires the fields `org_slug`, `pipeline_slug`, `build_number`, `job_id`, and `artifact_id`. Existing calls using the old schema will fail.

Why it matters: Affects all consumers of the get_artifact API – updates are required before v1.4.0 adoption to avoid request failures.

Summary

AI summary

Removed url argument from get_artifact and replaced it with required structured identifiers.

Changes in this release

Type	Severity	Summary	CVE
Breaking	High	Removed `url` argument from `get_artifact` input schema. Removed `url` argument from `get_artifact` input schema. Source: llm_adapter@2026-06-05 Confidence: high	—
Breaking	High	Added required fields `org_slug`, `pipeline_slug`, `build_number`, `job_id`, `artifact_id` to `get_artifact` input schema. Added required fields `org_slug`, `pipeline_slug`, `build_number`, `job_id`, `artifact_id` to `get_artifact` input schema. Source: llm_adapter@2026-06-05 Confidence: high	—
Bugfix	Medium	Fixed mapping env syntax usage in Buildkite pipelines. Fixed mapping env syntax usage in Buildkite pipelines. Source: llm_adapter@2026-06-05 Confidence: high	—

Full changelog

What's Changed

[PB-1900] replace get_artifact url arg with structured identifiers by @nethsix in https://github.com/buildkite/buildkite-mcp-server/pull/281
fix: use mapping env syntax in Buildkite pipelines by @wolfeidau in https://github.com/buildkite/buildkite-mcp-server/pull/279

Tool changes

get_artifact input schema changed:

removed: url
added (all required): org_slug, pipeline_slug, build_number, job_id, artifact_id

The identifiers map directly onto the output of list_artifacts_for_build / list_artifacts_for_job (job_id + artifact id), so the two tools chain without parsing a URL. No other tools are affected.

New Contributors

@nethsix made their first contribution in https://github.com/buildkite/buildkite-mcp-server/pull/281

Full Changelog: https://github.com/buildkite/buildkite-mcp-server/compare/v1.3.0...v1.4.0

Breaking Changes

`get_artifact` input removed `url` argument and now requires the structured identifiers: org_slug, pipeline_slug, build_number, job_id, artifact_id.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track buildkite/buildkite-mcp-server

Get notified when new releases ship.

About buildkite/buildkite-mcp-server

Official MCP server for Buildkite. Create new pipelines, diagnose and fix failures, trigger builds, monitor job queues, and more.

All releases →