[FEATURE] Native Bitbucket Integration for Claude Code
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Claude Code currently offers tight GitHub integration (MCP server, PR workflows, issue management, CI/CD status checks), but has no equivalent support for Bitbucket. Many teams and enterprises rely on Bitbucket as their primary platform for source control, code review, and CI/CD, and are unable to fully leverage Claude Code’s collaborative workflow features.
Proposed Solution
Proposed Enhancement
Add first-class Bitbucket support to Claude Code, on par with the existing GitHub integration. This would include:
∙ Pull Request workflows: Reading, creating, reviewing, and commenting on Bitbucket PRs
∙ Issue management: Creating, updating, searching, and commenting on Bitbucket issues
∙ CI/CD integration: Viewing pipeline status, build logs, and triggering pipelines (Bitbucket Pipelines)
∙ Repository browsing: Fetching file contents, branches, tags, and commits via the Bitbucket API
∙ Webhook support: Subscribing to PR and pipeline activity for real-time feedback loops
∙ Self-hosted support: Many enterprises run Bitbucket Server/Data Center; supporting configurable instance URLs is critical for adoption
Why This Matters
∙ Bitbucket has significant adoption, especially among teams using the Atlassian ecosystem
∙ Teams using Bitbucket are currently limited in leveraging Claude Code’s collaborative features
∙ Supporting both platforms would make Claude Code a more platform-agnostic development tool
∙ Bitbucket’s API (REST-based) is well-documented and supports similar integration patterns to GitHub, making implementation feasible
Suggested Approach
A Bitbucket MCP server (analogous to the existing GitHub MCP server) would be the most natural integration path, keeping the architecture consistent and extensible.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
I work on multiple Bitbucket repositories and need access from the native Claude app to continue my work from the Desktop or mobile app.
Additional Context
Bitbucket is widely used in enterprise environments, especially within the Atlassian ecosystem, and would benefit from equally strong, native integration.
6 Comments
The Atlassian Rovo MCP server now supports bitbucket so this feels like it shouldn't be too far away
The Bitbucket MCP
+1. Could plain Git remote support be the unifying solution here? It would cover GitHub, GitLab, Bitbucket, and self-hosted setups at once. My use case: moving off GitHub to a self-hosted server, and I'd love this in the mobile app.
+1 Please support bitbucket.
This is still a real adoption blocker for Bitbucket-based engineering teams.
Claude Code already works well locally, but without native Bitbucket PR + Pipelines integration, it cannot participate in the governed SDLC workflow where reviews, merge checks, CI status, and audit history actually live.
Even a focused MVP would help a lot:
Is Bitbucket support being considered for the Claude Code roadmap?
I suppose that you need to focus on as few mcps as possible to avoid wasting tokens just for the tools definitions and GitHub is hands low the more adopted repository and has an highly integrated framework (pr, workflows, issues). Maybe you may create the sandbox with only the correct mcp (bitbicket, gitlab, gitea) after discovering the repository flavor in a programmatic way.
I really miss the option to use Claude code directly on my app without having to remotize a pc session to connect to my self hosted gitea instance.
+1 for Bitbucket support in the UI just like Github currently is