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

Bitrise Pipelines (BYOK) — connector documentation

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

What Bitrise Pipelines (BYOK) is for

Bitrise Pipelines (BYOK) lets an AI assistant read your own Bitrise Pipelines data through the Bitrise Pipelines API with a key you supply (personal access token). Read-only: 5 tools (list_pipelines, list_app_pipelines, get_pipeline, list_archived_builds, list_build_requests). 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.bitrise.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitrise Pipelines. Bitrise Pipelines 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 Bitrise pipelines are running right now?"
  • "Show the last Bitrise pipeline runs of my app on the main branch."
  • "Which stages and workflows did Bitrise pipeline 9f8e7d6c run and did they pass?"
  • "Which Bitrise builds of my app were archived in September 2026?"
  • "Does my Bitrise app have build requests waiting for approval?"

What it does

  • list_pipelines: List pipelines and standalone builds across all apps of an account or organization, newest first, with status code, branch, workflow, credit cost and times. Triggering user and commit message are left out.
  • list_app_pipelines: List one app's pipelines and standalone builds with status code, branch, workflow, credit cost and times; filter by branch, status, workflow, pipeline name, trigger event or date.
  • get_pipeline: Get one pipeline of an app: status, abort reason, trigger time, and its stages and workflows with their statuses and credit cost.
  • list_archived_builds: List archived builds of an app (up to 1000) between two Unix times, with status, branch, workflow, credit cost and finish time.
  • list_build_requests: List the open build requests of an app (builds waiting for approval), with creation time and pull request URL.

BYOK key

You bring your own Bitrise Pipelines personal access token (https://docs.bitrise.io/en/bitrise-platform/accounts/personal-access-tokens.html). 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.bitrise.io 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 Bitrise Pipelines API (api.bitrise.io) with a BYOK key; documentation: https://api-docs.bitrise.io/. 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 Bitrise Pipelines. Bitrise Pipelines 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 Bitrise Pipelines account.

Built for: Worldwide. Languages: English.