Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Bitbucket Repository Rules (BYOK) icon

Bitbucket Repository Rules (BYOK)

Read Bitbucket Cloud repository rules: branch restrictions, branching models, default reviewers, merge queues and forks with your own Atlassian API token

Unify Dynamics LLC

Documentation
Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderBitbucket Repository Rulesunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which branch protection rules does myteam/my-repo have?
Tools called
list_branch_restrictions
Show branch rule 7 of myteam/my-repo
Tools called
get_branch_restriction
What branching model does myteam/my-repo use?
Tools called
get_branching_model
Which branching model is currently applied to myteam/my-repo?
Tools called
get_effective_branching_model
Who is automatically added as reviewer in myteam/my-repo?
Tools called
list_effective_default_reviewers
Does myteam/my-repo have a merge queue and is it active?
Tools called
list_merge_queues

About

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.

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.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List branch restrictionsList a repository's branch permission and merge check rules: kind (push, delete, force, require_approvals_to_merge ...), branch pattern or type…
  • Get branch restrictionGet one branch restriction rule by id: kind, match kind, branch type or pattern and value.
  • Get branching modelGet the repository's branching model: branch type prefixes (feature, bugfix, release, hotfix) and the development and production branches.
  • Get effective branching modelGet the branching model actually applied to the repository (repository setting or project default).
  • List effective default reviewersList the people automatically added as reviewers to new pull requests (repository plus project defaults) with their reviewer type.
  • List merge queuesList the merge queues of a repository with uuid, name and state (ACTIVE, PAUSED, DRAINING, SUSPENDED, INACTIVE); optionally for one target branch.
  • Get merge queueGet one merge queue: uuid, name and state.
  • List merge queue pull requestsList the pull requests waiting in a merge queue: status, rank, queued time and pull request id, title and state.
  • List forksList the forks of a repository with full name, privacy, language, size and last update.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-bitbucket-repo-rules.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

More like this

More in Other

Celigo US (BYOK)

Read your Celigo integrator.io (US region) integrations, flows, run jobs, connections, scripts, tags and error counts with your own API token

Live · MCP + REST12 tools

Dremio Cloud (BYOK)

Read your Dremio Cloud projects, engines, catalog objects, job status, reflections and saved scripts with your own personal access token

Live · MCP + REST9 tools

Astronomer (BYOK)

Read your Astro (managed Apache Airflow) organizations, workspaces, deployments, deploys, clusters, users and teams with your own API token

Live · MCP + REST10 tools

Datafold (BYOK)

Read your Datafold data sources, data diffs, monitors and monitor runs, CI runs and table lineage with your own API key

Live · MCP + REST11 tools

Holistics (BYOK)

Read your Holistics dashboards, data schedules, alerts, users, groups, data sources and job status with your own API key

Live · MCP + REST11 tools

Klipfolio (BYOK)

Read your Klipfolio dashboards, Klips, data sources, clients, groups and roles with your own API key

Live · MCP + REST10 tools

Get Bitbucket Repository Rules (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Bitbucket Repository Rules Atlassian API token with Bitbucket read scopes (repository and pull request). Create one at https://id.atlassian.com/manage-profile/security/api-tokens, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Bitbucket Repository Rules. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Bitbucket Repository Rules.