Buildkite Connector for AI agents.
11 live capabilities
Manage CI/CD pipelines and trigger builds without leaving your IDE.
Waiting for input…
Why people use Buildkite
Buildkite for Faster CI/CD Pipeline Management
With the Buildkite MCP, that whole process disappears. You just tell your AI client to find the failed build and show you the status. It pulls the data directly into your workspace, so you can focus on fixing the code instead of hunting for logs.
What Vinkius changes
You stop tab switching and start managing builds via natural conversation.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Stop a hung build
A build hangs at 50%.
- Real-world use case 02
Ad-hoc testing
An engineer wants to test a fix.
- Real-world use case 03
Status check
A lead wants to know the health of the frontend project.
Complete set · 11capabilities
The complete Buildkite capability set.
These are the exact actions your AI can choose when you ask it to work with Buildkite.
01—04
4 capabilities in this set.
Part of 11 available through Buildkite.
- 01 Capability
Cancel build
Stop a running build immediately to free up resources or stop a bad deployment. This is useful for clearing stuck jobs quickly.
- 02 Capability
Create build
Start a new build execution for a specific pipeline using natural language. You can use this to trigger tests on demand.
- 03 Capability
Get access token info
Check the status and details of your current Buildkite API token. This helps ensure your credentials are valid.
- 04 Capability
Get build
Pull specific details and status for a single build execution. Use this to see why a specific job failed.
05—08
4 capabilities in this set.
Part of 11 available through Buildkite.
- 05 Capability
List all builds
Get a complete list of every build across your entire organization. This provides a high level view of all activity.
- 06 Capability
List organizations
See all organizations that your current API token has permission to access. This is useful for multi-org management.
- 07 Capability
List pipeline builds
View all builds associated with a specific pipeline. Use this to check the history of a single project.
- 08 Capability
List pipelines
Get a full list of all pipelines within your organization. This lets you see every project your team manages.
09—11
3 capabilities in this set.
Part of 11 available through Buildkite.
- 09 Capability
Rebuild
Trigger a new run for a specific build that previously failed. This helps you quickly retry jobs that didn't finish.
- 10 Capability
Get pipeline
Retrieve the configuration and details for a specific pipeline. This helps you understand your current CI/CD setup.
- 11 Capability
List agents
See all build agents in your organization and check their current status. Use this to monitor your runner fleet.
Set up in minutes
One URL. Then ask Buildkite to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Buildkite from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Buildkite, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Buildkite for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Buildkite URL.
- Step 03
Save and start
Save the connection and enable Buildkite in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"buildkite": {
"url": "https://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp"
}
}
} - Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Buildkite
Open Agent mode in chat and ask: "Using Buildkite, help me...". 11 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"buildkite": {
"url": "https://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp"
}
}
} - Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Buildkite
Ask Copilot: "Using Buildkite, help me...". 11 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"buildkite": {
"url": "https://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp"
}
}
} - Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Buildkite
Open Cascade and ask: "Using Buildkite, help me...". 11 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"buildkite": {
"url": "https://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp"
}
}
} - Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Buildkite
Ask Cline: "Using Buildkite, help me...". 11 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add buildkite --transport http "https://edge.vinkius.com/vk_preview_iJnzptPh1up5uFxxYPxktlrRgHppLRL6cNlatVoW/mcp" - Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Buildkite
Ask Claude: "Using Buildkite, show me...". 11 tools are ready
Where the request belongs
Work Buildkite can move forward.
For the DevOps engineer who's tired of clicking through dashboards at 2am to find a hanging build, or the software engineer who wants to trigger test runs without leaving their IDE.
DevOps Engineer
Monitors agent health and manages hybrid CI infrastructure without manual dashboard navigation.
Software Engineer
Triggers ad-hoc test runs on feature branches while staying focused on the code.
Tech Lead
Gets quick summaries of build failure rates across the company to make informed merge decisions.
When one Connector is not enough
Carry the request into a workflow.
Combine Buildkite with the systems that finish the task.
View all recipesDebug CI Pipeline Failures Faster Using MCP
Your CI pipeline takes 47 minutes and nobody knows which step is the bottleneck , your AI agent analyzes every build, identifies the slow steps, and posts a weekly efficiency report
MCP Workflow for Automated Release Notes
PRs merged, builds validated, changelogs written, release pages published , generate polished release notes without copy-pasting commits
MCP Workflow for Container Build Monitoring
Pipelines monitored, build times tracked, image sizes audited, flaky steps flagged , keep your CI healthy without watching build logs
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsSemaphore
Automate CI/CD workflows, manage pipelines, and monitor build jobs directly from your AI agent.
Travis CI
Manage CI/CD pipelines, trigger custom builds, and oversee repository testing health securely via your AI agent.
Codefresh
Manage CI/CD and GitOps via Codefresh. track pipelines, trigger builds, and monitor delivery clusters directly from any AI agent.
Woodpecker CI
Manage your Woodpecker CI instance. control pipelines, monitor agents, and configure repositories directly from your AI agent.
CircleCI
Manage CI/CD pipelines and workflows via CircleCI. track jobs, trigger pipelines, and monitor build status directly from any AI agent.
Harness
Automate CI/CD and DevOps workflows via Harness. manage pipelines, executions, and secrets directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep Buildkite connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Buildkite.
The practical details behind the request, access and result.
Can I use the Buildkite MCP to start new builds?
Yes, it can trigger new build executions for any of your pipelines using natural language commands.
How does the Buildkite MCP help with failed deployments?
It lets you quickly retrieve specific build details to see exactly where a job failed, helping you troubleshoot faster.
Can I manage multiple organizations with the Buildkite MCP?
Yes, the Connector can list all organizations that your current API token has permission to access.
Does the Buildkite MCP work with my current AI client?
It works with any MCP-compatible client, including Claude, Cursor, and Windsurf.
Can I see which agents are running in my Buildkite account?
Yes, it can list all agents in your organization and provide their current status in real time.
Is the Buildkite MCP good for DevOps teams?
It is an excellent capability for DevOps teams because it centralizes build management and agent monitoring in a single chat interface.
Can my AI agent restart failed builds for a specific branch?
Yes. Ask the agent to find failed builds across your pipeline by using the list builds capability. Once it locates the specific build number, it can run the rebuild capability instantly, eliminating the need to search through hundreds of logs on the dashboard.
How can I check the status of my physical runner agents?
Ask your agent to list all agents connected to the Buildkite organization. It returns their UUIDs, operating systems, and connection state. If a runner hangs offline, your AI can immediately flag it to the Platform team, saving crucial deployment time.
If a commit is pushed to 'main', can the agent trigger a fresh pipeline deployment?
Absolutely. You can provide the commit SHA (or simply ask it to target 'HEAD' on the 'main' branch) and ask the agent to create a new build. It will hit the Buildkite trigger endpoint with a message of your choosing.
One connection away
Give your agent a direct line to Buildkite.
Connect Buildkite once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available