Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Buildkite (BYOK) — connector documentation

  • MCP endpoint: https://byok-buildkite.connectorbay.com/mcp
  • REST API: POST https://byok-buildkite.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-buildkite.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Buildkite API access token (with read_user, read_organizations, read_pipelines and read_builds scopes), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-buildkite.connectorbay.com/health · Tool schemas: https://byok-buildkite.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-buildkite · agent@connectorbay.com

What Buildkite (BYOK) is for

Buildkite (BYOK) lets an AI assistant read your own Buildkite data through the Buildkite API with a key you supply (API access token (with read_user, read_organizations, read_pipelines and read_builds scopes)). Read-only: 9 tools (get_current_user, get_access_token_info, list_organizations, get_organization, list_pipelines, get_pipeline, list_pipeline_builds, list_organization_builds, get_build). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.buildkite.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Buildkite. Buildkite and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Buildkite user is my token connected to?"
  • "Which scopes does my Buildkite token have?"
  • "Which Buildkite organizations do I belong to?"
  • "Show my Buildkite organization"
  • "Which Buildkite pipelines have builds running now?"
  • "Show details of my Buildkite pipeline"

What it does

  • get_current_user: Show the Buildkite user the token belongs to: name, email and account creation date. Needs the read_user scope.
  • get_access_token_info: Show metadata of the Buildkite access token in use: description, scopes, creation and expiry time. The token secret is not returned.
  • list_organizations: List the Buildkite organizations the token can access with name, slug and creation date. Needs the read_organizations scope.
  • get_organization: Get one Buildkite organization by slug: name, slug, web URL and creation date.
  • list_pipelines: List the pipelines of a Buildkite organization with repository, default branch, visibility and counts of running and scheduled builds and jobs. Needs the read_pipelines scope.
  • get_pipeline: Get one Buildkite pipeline by slug: repository, default branch, visibility, cluster and running or scheduled build and job counts.
  • list_pipeline_builds: List builds of one Buildkite pipeline, newest first, with state, branch, commit, message, creator and timestamps. Needs the read_builds scope.
  • list_organization_builds: List builds across all pipelines of a Buildkite organization, newest first, with pipeline, state, branch, commit and timestamps.
  • get_build: Get one Buildkite build by number: state, branch, commit, message, creator, timestamps and (when exclude_jobs is false) its jobs.

BYOK key

You bring your own Buildkite API access token (with read_user, read_organizations, read_pipelines and read_builds scopes) (https://buildkite.com/user/api-access-tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.buildkite.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Buildkite API (api.buildkite.com) with a BYOK key; documentation: https://buildkite.com/docs/apis/rest-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Buildkite. Buildkite and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Buildkite account.

Built for: Worldwide. Languages: English.