How to integrate Buildkite MCP with Atomic Agent

Connect Atomic Agent 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.

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

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,700+ apps through Composio, including Buildkite.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Buildkite account. See the Atomic Agent documentation for installation instructions.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Buildkite with

How Atomic Agent connects to Buildkite

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect Buildkite to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in Buildkite. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your Buildkite account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the Buildkite MCP server, 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.

Use Buildkite from Atomic Agent

With your account connected, ask Atomic Agent to work with Buildkite in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

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

List organizations available to the current API token, including organization slugs.

List Pipeline Agents

Tool to list connected agents for an organization.

FAQ

Frequently asked questions

Start with Buildkite.It takes 30 seconds.

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

Start building