How to Use the Buildkite MCP in Claude

Q: What happens if a Buildkite job gets stuck while I am chatting in Claude Desktop?

Ask your Claude Desktop agent to run listagents to check for idle Buildkite runners. If a Buildkite build is hung, tell Claude Desktop to invoke cancelbuild and then rebuild to try again.

Trigger Buildkite pipelines, monitor failing tests, and kick off rebuilds directly from your Claude Desktop chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Buildkite MCP to Claude Desktop

Create your Vinkius account to connect Buildkite to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Buildkite with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Rebuild and trigger pipelines in Claude Desktop

Instruct Claude Desktop to restart a broken Buildkite run using `rebuild` or launch a fresh run with `create_build` when a CI build fails. With this MCP Server, you bypass the manual browser steps entirely. The Buildkite API handshake happens directly inside Claude Desktop behind the scenes. Your Claude Desktop agent targets specific Buildkite branches or commit hashes, letting you fix a typo and immediately kick off the test suite.

Check agent health and active queues

Ask Claude Desktop to run `list_agents` and inspect `list_all_builds` if Buildkite jobs are stalling in your self-hosted queue. It helps you identify blocked runs before they slow down your entire team. You get a clear picture of your Buildkite infrastructure right in your Claude Desktop conversation. No more logging into the Buildkite web dashboard just to see why a runner isn't picking up a Claude Desktop build.

Debug pipeline failures directly in your chat

Let your Claude Desktop agent pull Buildkite build metadata with `get_build` and `list_pipeline_builds` instead of copying and pasting raw terminal logs. This lets Claude Desktop analyze why a Buildkite step failed and suggest the exact code fix you need. Use `cancel_build` on Claude Desktop if you realize a Buildkite run is doomed, saving your team precious build minutes. It keeps your development loop tight and fast with this MCP integration.

Setup guide

Set up Buildkite MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Buildkite MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Buildkite MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under buildkite-mcp.

json

{
  "mcpServers": {
    "buildkite-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Buildkite. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Buildkite now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Buildkite MCP in Claude Desktop

You open your local Claude Desktop config file and add the Buildkite server settings under the mcpServers block with your Buildkite API token. Once you restart Claude Desktop, the hammer icon will show the Buildkite tools are ready to run.

Yes, instruct Claude Desktop to start a Buildkite run on any branch. The Claude Desktop agent uses `create_build` with your parameters to target the exact Buildkite branch you need.

You just need a standard Buildkite API token with permissions to read and write builds inside Claude Desktop. As long as your Buildkite token has access to your organization, the Claude Desktop server can run commands.

Ask your Claude Desktop agent to run `list_agents` to check for idle Buildkite runners. If a Buildkite build is hung, tell Claude Desktop to invoke `cancel_build` and then `rebuild` to try again.

Your Buildkite API credentials and Buildkite build metadata never leave your local machine running Claude Desktop. The Buildkite MCP Server runs inside a secure local sandbox, ensuring your organization's sensitive pipeline data remains strictly private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript