Buildkite

The exported Go API of this module should be considered unstable, and subject to breaking changes as we evolve this project.

To ensure the MCP server is run in a secure environment, we recommend running it in a container.

Passing identity headers through HTTP mode

Self-hosted HTTP deployments can forward selected headers from each inbound MCP request to the Buildkite API:

BUILDKITE_API_TOKEN=bkua_xxx \ buildkite-mcp-server http \ --passthrough-http-header X-User-Identity

Repeat--passthrough-http-headerto allow more than one header, or set a comma-separatedBUILDKITE_PASSTHROUGH_HTTP_HEADERSvalue. Only explicitly allowed headers are forwarded, and only to the origin configured byBUILDKITE_BASE_URL. They are removed from requests redirected elsewhere.

To authenticate each MCP request with its own Buildkite API token, allowAuthorizationand omit the process-wide token:

BUILDKITE_PASSTHROUGH_HTTP_HEADERS=Authorization \ buildkite-mcp-server http

In this mode every/mcprequest must contain exactly one non-emptyAuthorizationheader. Missing credentials return HTTP 401; the server never falls back to a shared API token. The reverse proxy in front of the MCP server is responsible for authenticating callers and setting or validating any forwarded identity headers.

Header passthrough is not available in stdio mode. Before serving job logs, the server verifies that the current caller can access the job log. This check is performed for every log-tool request, including when the log data is already cached.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

The Octopus MCP Server provides your AI assistant with powerful tools that allow it to inspect, query, and diagnose problems within your Octopus instance, transforming it into your ultimate DevOps wingmate.

The Railway MCP Server enables natural language interaction with your Railway projects and infrastructure. Ask your IDE or AI assistant to create projects, deploy templates, manage environments, pull variables, redeploy services, and more.

The Shipyard CLI provides an MCP server for agents to manage Shipyard environments directly: by pulling logs, comparing branches, running tests, and stopping/starting environments..

MCP server for managing Unleash feature flags and automate best practices.

Integrates with AWS CodePipeline to manage continuous integration and delivery pipelines.

Manage apps, builds, and artifacts on Bitrise, a Continuous Integration and Delivery (CI/CD) platform.

Paid remote MCP for CLI tool MCP, structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.

A flexible MCP server that executes arbitrary command-line tools defined in a configuration file.

A Model Context Protocol (MCP) server for DeployHQ that enables AI assistants like Claude Desktop and Claude Code to interact with your DeployHQ deployments.