Integration

Buildkite integration

Buildkite REST API for managing CI/CD pipelines, builds, jobs, agents, teams, artifacts, and annotations. Trigger builds, monitor build state, retrieve job logs and artifacts, manage organization pipelines and self-hosted agents. Essential for build orchestration, deployment automation, and DevOps observability.

Connect Buildkite How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Buildkite.Built from the 25 Buildkite tools below, on the connection you add once.

Common Buildkite use cases

Retry flaky tests
Discover org slugs
Stop a stuck build
Inspect org metadata
Monitor agent health
Update pipeline YAML
Discover artifact ids
Inspect pipeline YAML
Monitor latest builds
Verify granted scopes

What you can do with Buildkite

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Pipeline, 6 operations

archive_pipelineArchive pipelinePOSTArchives a Buildkite pipeline.
create_pipelineCreate pipelinePOSTCreates a new Buildkite pipeline.
delete_pipelineDelete pipelineDELETEDeletes a Buildkite pipeline.
get_pipelineGet pipelineGETRetrieves a single Buildkite pipeline by slug.
list_pipelinesList pipelinesGETLists Buildkite pipelines in an organization.
update_pipelineUpdate pipelinePATCHUpdates a Buildkite pipeline's configuration.

Build, 5 operations

cancel_buildCancel buildPUTCancels a Buildkite build.
create_buildCreate buildPOSTTriggers a new Buildkite build on a pipeline.
get_buildGet buildGETRetrieves a single Buildkite build by its number.
list_buildsList buildsGETLists builds for a Buildkite pipeline with state/branch/commit/date filters.
rebuild_buildRebuild buildPUTRebuilds an existing Buildkite build.

Agent, 2 operations

list_agentsList agentsGETLists Buildkite agents currently connected to an organization.
stop_agentStop agentPUTStops a Buildkite agent.

Annotation, 2 operations

create_build_annotationCreate build annotationPOSTCreates or updates a Buildkite build annotation.
list_build_annotationsList build annotationsGETLists annotations attached to a Buildkite build.

Artifact, 2 operations

download_artifactDownload artifactGETDownloads a Buildkite build artifact as a file.
list_build_artifactsList build artifactsGETLists artifacts uploaded by a Buildkite build.

Job, 2 operations

retry_jobRetry jobPUTRetries a failed Buildkite job.
unblock_jobUnblock jobPUTUnblocks a Buildkite block-step job.

Job log, 2 operations

delete_job_logDelete job logDELETEDeletes a Buildkite job's log.
get_job_logGet job logGETRetrieves the structured log for a Buildkite job.

Organization, 2 operations

get_organizationGet organizationGETRetrieves a Buildkite organization by slug.
list_organizationsList organizationsGETLists Buildkite organizations the user can access.

Access token, 1 operation

get_access_tokenGet access tokenGETReturns metadata for the current Buildkite API access token.

User, 1 operation

get_userGet userGETRetrieves the authenticated Buildkite user profile.

Use Buildkite from Claude Code, Cursor or Codex

Connect Buildkite in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Buildkite operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Buildkite

Create your workspace
Sign up free. Nothing to install.
Connect Buildkite once
Add your Buildkite connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Buildkite integration FAQ

What can you do with the Buildkite integration?

LiveContext exposes 25 operations on Buildkite, covering pipeline, build, agent and annotation. Common uses include Retry flaky tests, Discover org slugs and Stop a stuck build.