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

Bitbucket Pipelines (BYOK) — connector documentation

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

What Bitbucket Pipelines (BYOK) is for

Bitbucket Pipelines (BYOK) lets an AI assistant read your own Bitbucket Pipelines data through the Bitbucket Pipelines API with a key you supply (Atlassian API token with Bitbucket read scopes (pipeline and repository)). Read-only: 12 tools (get_pipeline, list_pipeline_steps, get_pipeline_step, get_pipelines_config, list_pipeline_schedules, list_pipeline_caches, list_repository_runners, list_workspace_runners, list_deployments, get_deployment, list_environments, get_environment). 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.bitbucket.org. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Bitbucket Pipelines. Bitbucket 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:

  • "How did pipeline {1b2c3d4e-0000-4000-8000-000000000001} of myteam/my-repo end?"
  • "Which steps did pipeline {1b2c3d4e-0000-4000-8000-000000000001} of myteam/my-repo run and which failed?"
  • "Show step {2c3d4e5f-0000-4000-8000-000000000002} of pipeline {1b2c3d4e-0000-4000-8000-000000000001} in myteam/my-repo"
  • "Are Pipelines turned on for myteam/my-repo?"
  • "Which scheduled pipelines does myteam/my-repo have?"
  • "How big are the pipeline caches of myteam/my-repo?"

What it does

  • get_pipeline: Get one pipeline run: build number, state and result, branch or tag, trigger, creator, times and build minutes used.
  • list_pipeline_steps: List the steps of a pipeline run with UUID, state, result and times; commands and images are left out.
  • get_pipeline_step: Get one pipeline step: state, result and start and completion time; commands and images are left out.
  • get_pipelines_config: Show whether Bitbucket Pipelines is enabled for a repository.
  • list_pipeline_schedules: List a repository's scheduled pipelines with cron pattern, target and enabled flag.
  • list_pipeline_caches: List a repository's pipeline caches with name, path, size in bytes and creation time.
  • list_repository_runners: List the self-hosted Pipelines runners registered to a repository with labels, status and version.
  • list_workspace_runners: List the self-hosted Pipelines runners registered to a workspace with labels, status and version.
  • list_deployments: List a repository's deployments with environment, release name, state and deploy dates.
  • get_deployment: Get one deployment by UUID: state and status, environment, release and dates.
  • list_environments: List a repository's deployment environments (for example Test, Staging, Production) with name and UUID.
  • get_environment: Get one deployment environment by UUID with its name.

BYOK key

You bring your own Bitbucket Pipelines Atlassian API token with Bitbucket read scopes (pipeline and repository) (https://id.atlassian.com/manage-profile/security/api-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.bitbucket.org 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 Bitbucket Pipelines API (api.bitbucket.org) with a BYOK key; documentation: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pipelines/. 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 Bitbucket Pipelines. Bitbucket 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 Bitbucket Pipelines account.

Built for: Worldwide. Languages: English.