Documentation

Bitbucket connector

Index files from a Bitbucket Cloud repository into the knowledge corpus, and use live MCP tools to list repos, pull requests, and issues. Auth is a username + app password stored KMS-encrypted in connector_credentials.

Connect

  1. In Bitbucket, create an app password with account / workspace membership and repository read.
  2. In the OrgMCP admin console, open Connectors → Add → Bitbucket.
  3. Paste the username and app password, then click Test connection. A green result proves the password can see at least one workspace. 0 workspaces fails Test.

What gets indexed

  • One bitbucket_repo source per workspace/repoSlug (Bitbucket fullName). Optional ref, paths, and ignorePaths match the GitLab filters.
  • Tip-SHA short-circuit on the 6h cron tick; a 24h reconcile re-walks. Text and source extensions only. Indexing stops at a 1000-file cap and writes a Partial sync warning.

Honesty

  • bitbucket_diagnose and admin Test show the authenticated account plus workspace counts. 0 workspaces ⇒ Test red.
  • Listing repositories in a workspace that returns an empty first page is permission_denied, not a silent empty list.
  • A 0-chunk crawl writes an exact emptyReason (empty ref, path filter, only binaries).

Sources UI

The Index tab uses the flat snapshot list. Top-level discovery lists workspaces; drill-down lists repositories. Only bitbucket_repo rows are pickable ingest targets.