X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Buildkite to Claude

Connect Claude Web, Desktop and Cowork to Buildkite MCP. List all connected agents for your org, fetch buildkite api metadata for firewall setup, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Buildkite logoBuildkite
Api Key

Buildkite is a fast, secure CI/CD platform for running pipelines on your own infrastructure. It helps teams automate builds, tests, and deployments while keeping code and secrets private.

5 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Buildkite account to Claude via Composio Connect, enabling it to list all connected agents for your org, fetch Buildkite API metadata for firewall setup, verify your Buildkite API access token details, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Buildkite with

OpenAI Agents SDKClaude Agent SDKClaude CodeCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Buildkite to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Buildkite account

Back in Claude, ask it to connect to Buildkite or give it any Buildkite-related task.

For example, ask Claude to:

  • "List all connected agents for your org"
  • "Fetch Buildkite API metadata for firewall setup"
  • "Verify your Buildkite API access token details"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Buildkite account is ready to use.

What is the Buildkite Claude Connector, and what's possible with it?

The Buildkite MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Buildkite account. It provides structured and secure access to your CI/CD platform, so your agent can perform actions like verifying API access, retrieving build metadata, and listing connected pipeline agents on your behalf.

  • API token verification and management: Instantly confirm the validity, scopes, and details of your current Buildkite API token for secure automation and troubleshooting.
  • Buildkite API metadata retrieval: Fetch essential API metadata, including webhook IP addresses, to support your organization's firewall and security configurations.
  • Connected agent discovery: List all pipeline agents linked to your Buildkite organization, enabling dynamic monitoring and management of your CI/CD infrastructure.
  • Organization-wide agent filtering: Apply filters and pagination when retrieving agents, making it easy to manage large deployments and pinpoint specific resources.

Troubleshooting

1. Why does Claude not use the Composio connector for Buildkite?

The connector can show as connected, but Claude must use it in each Buildkite conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Buildkite again.

2. Why does Claude show an MCP server error before Buildkite connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Buildkite.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Buildkite.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Buildkite authorization link not work?

The Composio connector is one server. Your Buildkite account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Buildkite connection.
  • Composio creates a fresh Buildkite authorization link.
  • Open that link in your browser and finish the Buildkite sign-in.

4. Why do Buildkite actions fail after they worked before?

The Buildkite connection can expire or lose permission.

  • Ask Claude to inspect the Buildkite connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Buildkite account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Buildkite.
  • If the action still fails with a permission error, check that the connected account has that permission in Buildkite itself.

5. How do I switch to a different Buildkite account?

Claude can manage the Buildkite connection for you.

  • Ask Claude to disconnect or delete the current Buildkite account.
  • Ask Claude to connect Buildkite again.
  • Open the new Composio authorization link for Buildkite.
  • Sign in with the other Buildkite account in the browser.
  • After the account connects, ask Claude to retry the Buildkite task.

6. Why is my Buildkite connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Buildkite connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Buildkite tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Buildkite.
TOOLS

Supported Tools

Every Buildkite action and event your agent gets out of the box.

Get Current Access Token

Tool to retrieve the authenticated API access token details.

Get Meta

Tool to retrieve metadata about the Buildkite API.

Get User

Tool to retrieve details about the current authenticated user.

List Organizations

Tool to list all organizations the current user is a member of.

List Pipeline Agents

Tool to list connected agents for an organization.

FRAMEWORKS

How to build Buildkite MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Buildkite MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Buildkite MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Buildkite MCP with Claude Code

Codex logo

Codex

Use Buildkite MCP with Codex

OpenClaw logo

OpenClaw

Use Buildkite MCP with OpenClaw

Hermes logo

Hermes

Use Buildkite MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Buildkite MCP with Atomic Agent

Google ADK logo

Google ADK

Use Buildkite MCP with Google ADK

LangChain logo

LangChain

Use Buildkite MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Buildkite MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Buildkite MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Buildkite MCP with LlamaIndex

CrewAI logo

CrewAI

Use Buildkite MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Buildkite MCP with Pydantic AI

AutoGen logo

AutoGen

Use Buildkite MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Buildkite MCP server, the agents and LLMs can only access a fixed set of Buildkite tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Buildkite and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Buildkite tools.

Yes, absolutely. You can configure which Buildkite scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Buildkite data and credentials are handled as safely as possible.

Start with Buildkite.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Buildkite tool your agent needs.Free to start.

Start building