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

Buildkite Test Engine (BYOK) — connector documentation

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

What Buildkite Test Engine (BYOK) is for

Buildkite Test Engine (BYOK) lets an AI assistant read your own Buildkite Test Engine data through the Buildkite Test Engine API with a key you supply (API access token (with the read_suites scope)). Read-only: 6 tools (list_suites, list_pipeline_suites, get_suite, list_runs, get_run, list_failed_executions). 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 Test Engine. Buildkite Test Engine 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 test suites does my-great-org have in Buildkite Test Engine?"
  • "Which test suites report from the my-pipeline pipeline?"
  • "Show the rspec test suite in Buildkite Test Engine"
  • "Did the latest rspec test runs pass?"
  • "Show test run 64374307-12ab-4b13-a3f3-6a408f644ea2 of the rspec suite"
  • "Which tests failed in run 64374307-12ab-4b13-a3f3-6a408f644ea2 of the rspec suite?"

What it does

  • list_suites: List an organization's Test Engine suites with slug, default branch and application name.
  • list_pipeline_suites: List the Test Engine suites that have recorded at least one run for a given pipeline.
  • get_suite: Get one Test Engine suite by slug.
  • list_runs: List the test runs of a suite, newest first, with branch, commit, state and result (passed or failed).
  • get_run: Get one test run with branch, commit, state, result and the Buildkite build it belongs to.
  • list_failed_executions: List the failed test executions of one run with test name, location, failure reason, duration and tags.

BYOK key

You bring your own Buildkite Test Engine API access token (with the read_suites scope) (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 Test Engine API (api.buildkite.com) with a BYOK key; documentation: https://buildkite.com/docs/apis/rest-api/test-engine/suites. 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 Test Engine. Buildkite Test Engine 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 Test Engine account.

Built for: Worldwide. Languages: English.