Buildkite

​

At a glance

• Availability: Experimental (how to enable).
• Authentication: API key.
• Connection: The key comes from BUILDKITE_API_TOKEN.
• Provider documentation: Authentication reference.

​

Credentials

Set these per environment. See Connect an integration.

​

Setup

1. Sign in to Buildkite: Use an existing organization or create one at https://buildkite.com - free plans include API access. You need at least one pipeline to query builds.
2. Create an API access token: Go to https://buildkite.com/user/api-access-tokens, create a token scoped to your organization, and enable the read_pipelines, read_builds, and read_organizations REST scopes. Add write_builds if you want to trigger builds.
3. Set the environment variable: Add the token to your .env as BUILDKITE_API_TOKEN=…
4. Verify access: Run List Organizations, then List Pipelines with your organization slug.

​

Provider notes

• Requests authenticate with ‘Authorization: Bearer <token>’ against https://api.buildkite.com/v2
• API tokens are scoped per organization and per REST scope - missing scopes return 403
• Pagination uses page and per_page query parameters (max 100 per page)

Provider API reference.

​

Tools

​

Verify the connection

Call a read tool such as buildkite__list_organizations with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.