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

Bitbucket Repository Rules (BYOK) — connector documentation

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

What Bitbucket Repository Rules (BYOK) is for

Bitbucket Repository Rules (BYOK) lets an AI assistant read your own Bitbucket Repository Rules data through the Bitbucket Repository Rules API with a key you supply (Atlassian API token with Bitbucket read scopes (repository and pull request)). Read-only: 9 tools (list_branch_restrictions, get_branch_restriction, get_branching_model, get_effective_branching_model, list_effective_default_reviewers, list_merge_queues, get_merge_queue, list_merge_queue_pull_requests, list_forks). 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 Repository Rules. Bitbucket Repository Rules 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 branch protection rules does myteam/my-repo have?"
  • "Show branch rule 7 of myteam/my-repo"
  • "What branching model does myteam/my-repo use?"
  • "Which branching model is currently applied to myteam/my-repo?"
  • "Who is automatically added as reviewer in myteam/my-repo?"
  • "Does myteam/my-repo have a merge queue and is it active?"

What it does

  • list_branch_restrictions: List a repository's branch permission and merge check rules: kind (push, delete, force, require_approvals_to_merge ...), branch pattern or type and numeric value.
  • get_branch_restriction: Get one branch restriction rule by id: kind, match kind, branch type or pattern and value.
  • get_branching_model: Get the repository's branching model: branch type prefixes (feature, bugfix, release, hotfix) and the development and production branches.
  • get_effective_branching_model: Get the branching model actually applied to the repository (repository setting or project default).
  • list_effective_default_reviewers: List the people automatically added as reviewers to new pull requests (repository plus project defaults) with their reviewer type.
  • list_merge_queues: List the merge queues of a repository with uuid, name and state (ACTIVE, PAUSED, DRAINING, SUSPENDED, INACTIVE); optionally for one target branch.
  • get_merge_queue: Get one merge queue: uuid, name and state.
  • list_merge_queue_pull_requests: List the pull requests waiting in a merge queue: status, rank, queued time and pull request id, title and state.
  • list_forks: List the forks of a repository with full name, privacy, language, size and last update.

BYOK key

You bring your own Bitbucket Repository Rules Atlassian API token with Bitbucket read scopes (repository and pull request) (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 Repository Rules API (api.bitbucket.org) with a BYOK key; documentation: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-branch-restrictions/. 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 Repository Rules. Bitbucket Repository Rules 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 Repository Rules account.

Built for: Worldwide. Languages: English.