Buildkite Config (BYOK) — connector documentation
- MCP endpoint:
https://byok-buildkite-config.connectorbay.com/mcp - REST API:
POST https://byok-buildkite-config.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-buildkite-config.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Buildkite Config API access token (with read_pipelines, read_teams and read_rules scopes), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-buildkite-config.connectorbay.com/health· Tool schemas:https://byok-buildkite-config.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-buildkite-config · agent@connectorbay.com
What Buildkite Config (BYOK) is for
Buildkite Config (BYOK) lets an AI assistant read your own Buildkite Config data through the Buildkite Config API with a key you supply (API access token (with read_pipelines, read_teams and read_rules scopes)). Read-only: 8 tools (list_pipeline_templates, get_pipeline_template, list_pipeline_schedules, get_pipeline_schedule, list_teams, get_team, list_rules, get_rule). 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 Config. Buildkite Config 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:
- "What pipeline templates does my-great-org have in Buildkite?"
- "Show the steps of Buildkite pipeline template 018a86cc-db73-7d15-8c68-5023cf8d64c3"
- "When do the scheduled builds of my-pipeline run?"
- "Show schedule b3a1e9f2-7c4d-4f1a-9e6c-2d8a5f7b1c3d of my-pipeline"
- "What teams does my-great-org have in Buildkite?"
- "Show Buildkite team c5e09619-8648-4896-a936-9d0b8b7b3fe9"
What it does
list_pipeline_templates: List an organization's pipeline templates with name, description and whether each is available for new pipelines.get_pipeline_template: Get one pipeline template including its YAML step configuration.list_pipeline_schedules: List a pipeline's scheduled builds with cron line, branch, commit, enabled flag and next run time (schedule environment variables are not returned).get_pipeline_schedule: Get one scheduled build of a pipeline.list_teams: List an organization's teams with privacy setting and whether each is a default team for new members.get_team: Get one team by UUID.list_rules: List an organization's access rules (which pipelines may trigger or artifact-share with which others) with source, target, effect and action.get_rule: Get one access rule by UUID.
BYOK key
You bring your own Buildkite Config API access token (with read_pipelines, read_teams and read_rules 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
- https://buildkite.com/docs/apis/rest-api/pipeline-templates (the API this connector calls, with a BYOK key)
Live from the Buildkite Config API (api.buildkite.com) with a BYOK key; documentation: https://buildkite.com/docs/apis/rest-api/pipeline-templates. 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 Config. Buildkite Config 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 Config account.
Built for: Worldwide. Languages: English.