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

Context

T3 Code's Bitbucket integration for the Source Control / Pull Requests panel currently requires server-side env vars:

• T3CODE_BITBUCKET_ACCESS_TOKEN, or
• T3CODE_BITBUCKET_EMAIL + T3CODE_BITBUCKET_API_TOKEN

Without those it shows 'Not authenticated' and operations like list fail (unauthenticated rate-limit errors against bitbucket.org).

Use case

I already have access to a custom internal MCP server that authenticates to Bitbucket on its own (OAuth via the MCP) and exposes PR/repository tools to the agent. The agent can list/get/diff/comment PRs through the MCP just fine.

But the native Pull Requests page / Source Control UI can't use it — it only understands the built-in token auth above.

Question / feature request

Is there any supported way to:

1. Plug a custom MCP (or its credentials) as the auth/backend for the native Bitbucket provider, so the Pull Requests panel uses it?
2. Or, alternatively, let the agent's MCP tools power that panel?

If not supported today, would you consider supporting custom auth providers for source control, or documenting a recommended workaround?

Thanks!

Start by tracing the native Bitbucket provider used by the Pull Requests panel and Source Control UI, then compare its existing T3CODE_BITBUCKET_* authentication path with the custom MCP use case. Done means a supported integration or documented workaround that lets the panel obtain Bitbucket data through the custom auth/backend, with the unauthenticated list failure addressed.