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 tool. Once it locates the specific build number, it can run the rebuild tool 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.

Buildkite MCP Server for Windsurf 11 tools — connect in under 2 minutes

Name: Buildkite
Availability: InStock
Author: Vinkius

docs.windsurf.com/windsurf/mcp

Built by Vinkius GDPR 11 Tools IDE

Windsurf brings agentic AI coding to a purpose-built IDE. Connect Buildkite through Vinkius and Cascade will auto-discover every tool. ask questions, generate code, and act on live data without leaving your editor.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Buildkite and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Buildkite MCP Server

Connect your Buildkite account to any AI agent and take full control of your CI/CD workflows through natural conversation.

Windsurf's Cascade agent chains multiple Buildkite tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 11 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.

What you can do

Pipelines & Builds — List active pipelines, trigger new builds, retry failed executions, or cancel stuck pipelines instantly
Deep Log Inspection — Retrieve the exact details of specific builds, examining job lists, statuses, and tracking links
Agent Management — Ping your connected build agents globally and verify their status
Organizational Overview — Monitor your organization's scale, retrieve active pipelines across the entire company, and get recent builds map

The Buildkite MCP Server exposes 11 tools through the Vinkius. Connect it to Windsurf in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Buildkite to Windsurf via MCP

Follow these steps to integrate the Buildkite MCP Server with Windsurf.

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"

Add the server

Paste the JSON configuration above into mcp_config.json

Save and reload

Windsurf will detect the new server automatically

Start using Buildkite

Open Cascade and ask: "Using Buildkite, help me...". 11 tools available

Why Use Windsurf with the Buildkite MCP Server

Windsurf provides unique advantages when paired with Buildkite through the Model Context Protocol.

Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention

Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively

JSON-based configuration means zero code changes: paste a URL, reload, and all 11 tools are immediately available

Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts

Buildkite + Windsurf Use Cases

Practical scenarios where Windsurf combined with the Buildkite MCP Server delivers measurable value.

Automated code generation: ask Cascade to fetch data from Buildkite and generate models, types, or handlers based on real API responses

Live debugging: query Buildkite tools mid-session to inspect production data while debugging without leaving the editor

Documentation generation: pull schema information from Buildkite and have Cascade generate comprehensive API docs automatically

Rapid prototyping: combine Buildkite data with Cascade's code generation to scaffold entire features in minutes

Buildkite MCP Tools for Windsurf (11)

These 11 tools become available when you connect Buildkite to Windsurf via MCP:

cancel_build

Cancel a running build

create_build

Trigger a new build for a pipeline

get_access_token_info

Retrieve information about the current API token

get_build

Get details of a specific build

get_pipeline

Get details of a specific pipeline

list_agents

List all build agents in the organization

list_all_builds

List all builds across the entire organization

list_organizations

List all organizations the token has access to

list_pipeline_builds

List builds for a specific pipeline

list_pipelines

List all pipelines in the organization

rebuild

Rebuild a specific build

Example Prompts for Buildkite in Windsurf

Ready-to-use prompts you can give your Windsurf agent to start working with Buildkite immediately.

"What recent builds ran on our production pipeline?"

"Cancel build #205 because of a wrong commit."

"Trigger a new build on HEAD of the main branch for our react-app."

Troubleshooting Buildkite MCP Server with Windsurf

Common issues when connecting Buildkite to Windsurf through the Vinkius, and how to resolve them.

Server not connecting

Check Settings → MCP for the server status. Try toggling it off and on.

Buildkite + Windsurf FAQ

Common questions about integrating Buildkite MCP Server with Windsurf.

How does Windsurf discover MCP tools?

Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.

Can Cascade chain multiple MCP tool calls?

Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.

Does Windsurf support multiple MCP servers?

Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.