Product and engineering

The Bitbucket connector.

Repos, pull requests, commits and pipelines. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.

How access is governed

6

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

Bitbucket exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

Bitbucket defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Bitbucket tool

6 tools, named as the agent sees them.

  • list_repositoriesread

    List repositories in a Bitbucket workspace, most recently updated first. Use this first — the returned `slug` is the repo_slug every other tool takes.

  • get_repositoryread

    Get one repository’s metadata. Takes the repo_slug from list_repositories.

  • list_pull_requestsread

    List pull requests in a repository — use this to see what is awaiting review. The returned `id` is what get_pull_request takes.

  • get_pull_requestread

    Get one pull request with its full description and merge state. Takes the repo_slug from list_repositories and the numeric `id` from list_pull_requests.

  • list_commitsread

    List recent commits on a repository branch. Takes the repo_slug from list_repositories.

  • list_pipelinesread

    List recent Bitbucket Pipelines runs for a repository — use this to check build health. Takes the repo_slug from list_repositories.

Use it from any agent

The same Bitbucket tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Bitbucket App Password in your Bitbucket account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in product and engineering

LinearCursorSentryAsanaClickUpNotion

Connect Bitbucket once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in