How to Use the Buildkite MCP in VS Code Copilot

Q: Can I cancel a running Buildkite build from VS Code Copilot?

Yes, tell the VS Code Copilot agent to run cancelbuild on any active Buildkite run. VS Code Copilot will find the Buildkite build ID and abort the process immediately.

Manage Buildkite builds, agents, and deployments directly from VS Code Copilot with team-wide shared configurations.

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 VS Code Copilot

Create your Vinkius account to connect Buildkite to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run Buildkite pipelines inside VS Code Copilot

Developers use `create_build` and `rebuild` directly from the VS Code Copilot chat panel by checking this configuration into git. By committing the configuration to your repository, your entire engineering team gets access to this MCP Server. This makes onboarding new developers to your Buildkite workflows incredibly fast. Anyone on the team triggers a Buildkite deployment or checks test statuses without leaving VS Code Copilot.

Monitor your build agents from the editor

Keep an eye on your self-hosted Buildkite runner infrastructure using `list_agents` and `list_all_builds` inside VS Code Copilot. If your build queue is backed up, your team can quickly identify the bottleneck directly from the chat UI. This visibility helps developers understand why their pull requests are stuck in the Buildkite queue directly from VS Code Copilot. You don't need to ping your DevOps team; the Buildkite data is right there in your VS Code Copilot chat.

Analyze Buildkite failures with Copilot Chat

Ask VS Code Copilot to fetch the details using `get_build` and `list_pipeline_builds` when a Buildkite build fails using this MCP integration. The VS Code Copilot agent reads the Buildkite failure logs and matches them against your local workspace files to find the bug. If the Buildkite failure is a known flaky test, run `rebuild` with a single command inside VS Code Copilot. It keeps your team's development momentum going without leaving the editor.

Setup guide

Set up Buildkite MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Buildkite MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Buildkite tools listed. Try asking: "List my recent Buildkite transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Commit a configuration file to your repository root under the .vscode directory. Once your team pulls the changes, VS Code Copilot will automatically discover the Buildkite server tools.

Yes, limit the scope of the Buildkite API token used by the server. The VS Code Copilot agent will only be able to run `create_build` or `list_pipelines` on the Buildkite pipelines permitted by your token.

The server uses a Buildkite API token that you provide during setup. The VS Code Copilot agent uses `get_access_token_info` to verify the Buildkite connection is active and has the correct permissions.

Yes, tell the VS Code Copilot agent to run `cancel_build` on any active Buildkite run. VS Code Copilot will find the Buildkite build ID and abort the process immediately.

No, all Buildkite build logs and pipeline configurations fetched by the server are processed locally within your editor. Your sensitive Buildkite API tokens and pipeline metadata are never transmitted to external AI endpoints or telemetry trackers.

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