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.

LiveContext

All integrations

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.

25 toolsTokenAPI docs

Connect Buildkite How integrations work

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

POSTarchive_pipeline
Archives a Buildkite pipeline.
POSTcreate_pipeline
Creates a new Buildkite pipeline.
DELETEdelete_pipeline
Deletes a Buildkite pipeline.
GETget_pipeline
Retrieves a single Buildkite pipeline by slug.
GETlist_pipelines
Lists Buildkite pipelines in an organization.
PATCHupdate_pipeline
Updates a Buildkite pipeline's configuration.

Build, 5 operations

PUTcancel_build
Cancels a Buildkite build.
POSTcreate_build
Triggers a new Buildkite build on a pipeline.
GETget_build
Retrieves a single Buildkite build by its number.
GETlist_builds
Lists builds for a Buildkite pipeline with state/branch/commit/date filters.
PUTrebuild_build
Rebuilds an existing Buildkite build.

Agent, 2 operations

GETlist_agents
Lists Buildkite agents currently connected to an organization.
PUTstop_agent
Stops a Buildkite agent.

Annotation, 2 operations

POSTcreate_build_annotation
Creates or updates a Buildkite build annotation.
GETlist_build_annotations
Lists annotations attached to a Buildkite build.

Artifact, 2 operations

GETdownload_artifact
Downloads a Buildkite build artifact as a file.
GETlist_build_artifacts
Lists artifacts uploaded by a Buildkite build.

Job, 2 operations

PUTretry_job
Retries a failed Buildkite job.
PUTunblock_job
Unblocks a Buildkite block-step job.

Job log, 2 operations

DELETEdelete_job_log
Deletes a Buildkite job's log.
GETget_job_log
Retrieves the structured log for a Buildkite job.

Organization, 2 operations

GETget_organization
Retrieves a Buildkite organization by slug.
GETlist_organizations
Lists Buildkite organizations the user can access.

Access token, 1 operation

GETget_access_token
Returns metadata for the current Buildkite API access token.

User, 1 operation

GETget_user
Retrieves 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.