Use custom MCP for Bitbucket auth in Pull Requests panel instead of T3CODE_BITBUCKET_*? #11882

Activity

1. juliusmarminge commented on Sep 15, 2026

   

   juliusmarminge

   on Sep 15, 2026

   Member

   More actions

   Thanks for the clear write-up. This is a real gap, but it is not supported today.

   The native Source Control / Pull Requests UI and the agent’s MCP tools are separate stacks.

   Native Bitbucket (PR panel, Settings → Source Control, clone/publish, Git actions) talks to Bitbucket Cloud over HTTP using only server env vars:

   • T3CODE_BITBUCKET_ACCESS_TOKEN (Bearer), or
   • T3CODE_BITBUCKET_EMAIL + T3CODE_BITBUCKET_API_TOKEN (Basic)

   T3CODE_BITBUCKET_API_BASE_URL only changes the API host; it does not change how auth is obtained. There is no settings field, OAuth login, or “use this MCP” option. Bitbucket is the one host that is type: "api" (env + HTTP). GitHub / GitLab / Forgejo / Azure DevOps use their CLIs instead.

   If those vars are unset, discovery still lists Bitbucket as available, probeAuth reports Not authenticated, and list/get still hit api.bitbucket.org without credentials (which is why you see unauthenticated rate-limit errors).

   Agent MCP is the other direction. A custom MCP you attach to a session is available to the model as tools. It does not implement PullRequestProvider and is never consulted by the PR page. T3’s own MCP pull-request toolkit (link_pull_request, thread PR listing, etc.) is T3 → agent, and it also does not authenticate Bitbucket for the UI.

   There is no custom source-control auth provider, no MCP-backed Bitbucket driver, and no way to reuse MCP OAuth tokens as T3CODE_BITBUCKET_*. GitHub sharing (use another environment’s gh creds) is GitHub-only and also not MCP.

   Workaround for the native panel: set one of the credential pairs on the T3 Code server process and restart, then Rescan in Settings → Source Control. The token needs pull request, repository, and user read (read:user:bitbucket). If your MCP can mint or export a Bitbucket access token, that value in T3CODE_BITBUCKET_ACCESS_TOKEN is the only supported way to feed the panel. Desktop/WSL env delivery is a known pain (#5840, #7621) — the vars have to reach the running server, not only a shell profile.

   Workaround without native UI: keep using the custom MCP from the agent for list/get/diff/comment. That path will not populate the Pull Requests page.

   Treating this as an enhancement: a first-class custom auth backend (or an MCP-backed source-control provider) would be new architecture, not a small hook. Leaving it open for product to decide whether to take that on. Related Bitbucket issues (#5840, #7621, #8328) are env-delivery / API bugs, not this request.
2. juliusmarminge

   added

   enhancementRequested improvement or new capability.Requested improvement or new capability.

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   on Sep 15, 2026
3. leo-mathurin commented on Sep 30, 2026

   

   leo-mathurin

   on Sep 30, 2026

   More actions

   Bitbucket Data Center please 🤠
4. pingdotgg

   locked and limited conversation to collaborators on Oct 11, 2026
5. maria-rcks

   converted this issue into a discussion #17987 on Oct 11, 2026