Buildkite

How to connect

• access_token

  Get information about the current API access token including its scopes and UUID

• create_build

  Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, metadata, and author information

• create_cluster

  Create a new cluster in an organization

• create_cluster_queue

  Create a new queue in a cluster

• create_pipeline

  Set up a new CI/CD pipeline in Buildkite with YAML configuration, repository connection, and cluster assignment

• current_user

  Get details about the user account that owns the API token, including name, email, avatar, and account creation date

• get_artifact

  Get detailed information about a specific artifact including its metadata, file size, SHA-1 hash, and download URL

• get_build

  Get build information including job IDs, names, and states. Use job_state to filter (e.g. 'failed,broken'). Returns enough detail to identify which jobs to investigate with log and artifact tools

• get_build_test_engine_runs

  Get test engine runs data for a specific build in Buildkite. This can be used to look up Test Runs.

• get_cluster

  Get detailed information about a specific cluster including its name, description, default queue, and configuration

• get_cluster_queue

  Get detailed information about a specific queue including its key, description, dispatch status, and hosted agent configuration

• get_failed_executions

  Get failed test executions for a specific test run in Buildkite Test Engine. Optionally get the expanded failure details such as full error messages and stack traces.

• get_pipeline

  Get detailed information about a specific pipeline including its configuration, steps, environment variables, and build statistics

• get_test

  Get a specific test in Buildkite Test Engine. This provides additional metadata for failed test executions

• get_test_run

  Get a specific test run in Buildkite Test Engine

• list_annotations

  List all annotations for a build, including their context, style (success/info/warning/error), rendered HTML content, and creation timestamps

• list_artifacts_for_build

  List all artifacts for a build across all jobs, including file details, paths, sizes, MIME types, and download URLs

• list_artifacts_for_job

  List all artifacts for an individual job, including file details, paths, sizes, MIME types, and download URLs

• list_builds

  List builds for a pipeline or across all pipelines in an organization. When pipeline_slug is omitted, lists builds across all pipelines in the organization

• list_cluster_queues

  List all queues in a cluster with their keys, descriptions, dispatch status, and agent configuration

• list_clusters

  List all clusters in an organization with their names, descriptions, default queues, and creation details

• list_pipelines

  List all pipelines in an organization with their basic details, build counts, and current status

• list_test_runs

  List all test runs for a test suite in Buildkite Test Engine

• pause_cluster_queue_dispatch

  Pause dispatch on a cluster queue, preventing new jobs from being dispatched to agents

• read_logs

  Read log entries from the file, optionally starting from a specific row number. ALWAYS use 'limit' parameter to avoid excessive tokens. For recent failures, use 'tail_logs' instead. Recommended limits: investigation (100-500), exploration (use seek + small limits). The json format: {ts: timestamp_ms, c: content, rn: row_number}.

• resume_cluster_queue_dispatch

  Resume dispatch on a paused cluster queue, allowing jobs to be dispatched to agents again

• search_logs

  Search log entries using regex patterns with optional context lines. For recent failures, try 'tail_logs' first, then use search_logs with patterns like 'error|failed|exception' and limit: 10-20. The json format: {ts: timestamp_ms, c: content, rn: row_number}.

• tail_logs

  Show the last N entries from the log file. RECOMMENDED for failure diagnosis - most build failures appear in the final log entries. More token-efficient than read_logs for recent issues. The json format: {ts: timestamp_ms, c: content, rn: row_number}.

• unblock_job

  Unblock a blocked job in a Buildkite build to allow it to continue execution

• update_cluster

  Update an existing cluster's name, description, emoji, color, or default queue

• update_cluster_queue

  Update an existing cluster queue's description or retry agent affinity

• update_pipeline

  Modify an existing Buildkite pipeline's configuration, repository, settings, or metadata

• user_token_organization

  Get the organization associated with the user token used for this request

Related servers