At a glance: Atlassian’s official Remote MCP Server (645 stars, Apache-2.0) now supports Jira, Confluence, Compass, and — as of April 8, 2026 — Bitbucket Cloud. The BCLOUD-23748 feature request that defined this review at launch has been answered: Atlassian’s Rovo MCP server added 7 Bitbucket tool categories covering workspaces, repositories, file contents, pull requests, pipelines, environments, and deployments. Community servers continue to serve supplemental needs: aashari/mcp-server-atlassian-bitbucket (146 stars, 6 generic REST tools), MatanYemini/bitbucket-mcp (132 stars, 25+ tools), and garc33/bitbucket-server-mcp-server (62 stars, 21 tools for Bitbucket Server/DC). The ecosystem still lags GitHub (28.2k-star official server) and GitLab (built-in official server + 1.2k-star community leader), but the critical gap — zero official Bitbucket MCP support — is closed.

Atlassian is a ~$6.4B annual revenue public company (NASDAQ: TEAM). The company completed a 10% workforce reduction (March 2026, ~1,600 employees) to fund AI development; CTO Rajeev Rajan departed March 31. Bitbucket serves approximately 41,000 companies with a 2.78% market share in source code management — a distant third behind GitHub (180M+ developers) and GitLab (30M+ users). Atlassian is not a member of the Agentic AI Foundation (AAIF). The company’s AI investment is concentrated on Rovo, its AI assistant, which now powers official MCP coverage across Jira, Confluence, Compass, and Bitbucket Cloud.

Architecture note: Atlassian’s Jira/Confluence MCP server launched without Bitbucket in late 2025, and that gap defined this review at launch. On April 8, 2026, Atlassian shipped Bitbucket Cloud support in their Rovo MCP server — 7 tool categories spanning the full Bitbucket workflow. The structural improvement is real, but two limitations remain: official support is Cloud-only (no Server/Data Center), and Bitbucket auth is currently API-token-only while Jira and Confluence have OAuth 2.1. Community servers remain necessary for Server/DC deployments. This is the third review in our Developer Tools MCP category.

Category: Developer Tools

What’s Available

Atlassian Official Remote MCP Server (Now Includes Bitbucket)

Atlassian’s first-party MCP server — updated April 8, 2026 to include Bitbucket Cloud:

AspectDetail
Repositoryatlassian/atlassian-mcp-server
Stars~645
ProductsJira, Confluence, Compass, Bitbucket Cloud (added April 8, 2026)
AuthenticationOAuth 2.1, API tokens (Bitbucket: API token only — OAuth on roadmap)
PricingFree for all Atlassian Cloud customers (rate-limited by plan)
LicenseApache-2.0

46+ tools covering Jira, Confluence, and Compass — plus 7 new Bitbucket tool categories announced April 8, 2026:

Bitbucket Tool CategoryCapabilities
bitbucketWorkspaceList and retrieve workspace information
bitbucketRepositoryList and access repositories within workspaces
bitbucketRepoContentManage branches, commits, and file contents
bitbucketPullRequestCreate, review, approve, comment, diff, and merge pull requests
bitbucketPipelineMonitor and trigger pipelines, view steps and logs
bitbucketEnvironmentManage deployment environments
bitbucketDeploymentTrack deployment status and history

Works with Claude, ChatGPT, GitHub Copilot CLI, Gemini CLI, VS Code, Cursor, and any MCP-compatible client. Rate limits: 500 calls/hour (Free), 1,000+ calls/hour (Standard/Premium/Enterprise).

BCLOUD-23748 resolved: The feature request that defined this review’s original “no official support” conclusion was addressed directly by this April 8 release.

Current limitations: Bitbucket tools require workspaces connected to an Atlassian organization. OAuth authentication for Bitbucket is not yet supported — API tokens only (OAuth is on the roadmap). Bitbucket Server/Data Center is not covered by the official server.

What this changes for Bitbucket users: Organizations using the full Atlassian stack (Jira + Confluence + Bitbucket) can now connect AI agents across all three platforms through a single, officially supported MCP server — including pipeline diagnostics, PR management, and code exploration. The community-only era is over for Bitbucket Cloud users.

MatanYemini/bitbucket-mcp (Most Tools)

The most feature-rich community Bitbucket MCP server:

AspectDetail
RepositoryMatanYemini/bitbucket-mcp
Stars~132
Forks~85
Commits69
LanguageTypeScript
LicenseMIT
TargetBitbucket Cloud

25+ tools focused heavily on pull request management:

CategoryTools
RepositorieslistRepositories, getRepository
Pull RequestsgetPullRequests, createPullRequest, getPullRequest, updatePullRequest, getPullRequestActivity, approvePullRequest, unapprovePullRequest, declinePullRequest, mergePullRequest, requestChanges, removeChangeRequest
Draft PRscreateDraftPullRequest, publishDraftPullRequest, convertToDraft
PR CommentsgetPullRequestComments

Key differentiator: Safety-first design — no DELETE operations are implemented. Pagination support with auto-fetching (capped at 1,000 entries). CodeQL security scanning on all pull requests. Docker support included. Configuration supports both API URL format and legacy web URL.

Limitation: Bitbucket Cloud only — no Server/Data Center support. No issue management (Bitbucket Cloud has issues, though most teams use Jira). No pipeline management. No file content access or code search.

aashari/mcp-server-atlassian-bitbucket (Most Stars Among Community Servers)

A leading community Bitbucket MCP server — still useful for its generic REST API approach:

AspectDetail
Repositoryaashari/mcp-server-atlassian-bitbucket
Stars~146
Forks~48
Commits595
LanguageTypeScript
NPM Package@aashari/mcp-server-atlassian-bitbucket

6 generic REST API tools:

ToolWhat it does
bb_getRetrieve data from any Bitbucket API endpoint
bb_postCreate resources via API endpoints
bb_putReplace resources via API endpoints
bb_patchApply partial updates to resources
bb_deleteRemove resources from endpoints
bb_cloneClone repositories locally

Key differentiator: Rather than building specific tools for each operation, this server exposes generic CRUD operations against the Bitbucket API. The LLM constructs the correct API paths. Uses TOON (Token-Oriented Object Notation) format that claims 30-60% fewer tokens than JSON. Supports JMESPath filtering for response customization. Dual auth: Scoped API Tokens and legacy App Passwords.

Limitation: Generic API tools put the burden on the LLM to know Bitbucket’s API structure. More error-prone than purpose-built tools. The tool count (6) is misleading — it’s really 5 HTTP verbs plus clone.

⚠️ App Passwords deprecation: Bitbucket App Passwords are being deprecated and will be removed by June 2026. Users of aashari’s server (and any server using App Passwords) must migrate to Scoped API Tokens before this deadline.

garc33/bitbucket-server-mcp-server (Server/DC)

The leading Bitbucket Server / Data Center MCP server:

AspectDetail
Repositorygarc33/bitbucket-server-mcp-server
Stars~62
Forks~41
Commits55
LanguageTypeScript
TargetBitbucket Server / Data Center

21 tools covering PR management, code discovery, and repository operations:

ToolWhat it does
list_projectsDiscover accessible Bitbucket projects
list_repositoriesBrowse repositories within projects
create_pull_requestSubmit code changes for review
get_pull_requestRetrieve detailed PR information
merge_pull_requestIntegrate with multiple merge strategies
decline_pull_requestReject pull requests
approve_pull_requestApprove code changes
unapprove_pull_requestRetract approvals
list_pull_requestsFilter PRs by state/author
add_commentParticipate in code review
get_diffAnalyze code changes
get_reviewsTrack review progress
get_activitiesRetrieve PR timeline
get_commentsExtract PR comments
searchAdvanced code/file search
get_file_contentRead file contents
browse_repositoryExplore repository structure
list_branchesExplore branches
list_commitsBrowse commit history
delete_branchClean up merged branches

Key differentiator: The only well-established MCP server targeting Bitbucket Server/Data Center. Custom HTTP header support via environment variable. Merge strategy selection. File content with pagination. This matters for enterprises that run Bitbucket on-premise and can’t use Cloud-only solutions.

Other Notable Servers

b1ff/atlassian-dc-mcp (59 stars, 175 commits, TypeScript, MIT) — Multi-product MCP server covering Jira, Confluence, and Bitbucket for Data Center deployments. Monorepo with separate packages per product (@atlassian-dc-mcp/bitbucket). Good for teams that want one MCP server for the full Atlassian DC stack.

Ibrahimogod/bitbucket-mcp (0 stars, Rust, MIT, 20+ tools) — High-performance Rust implementation with comprehensive Bitbucket Cloud API coverage including pipelines, deployments, webhooks, and snippets. Docker-ready via GHCR images. Well-engineered but zero adoption. The Rust implementation may appeal to performance-sensitive deployments.

sooperset/mcp-atlassian (4.7k stars, 558 commits, Python, MIT, 72 tools) — By far the most popular Atlassian MCP server, but it only supports Jira and Confluence — not Bitbucket. Mentioned here because users searching for “Atlassian MCP” will find this first and may assume it covers Bitbucket.

Developer Tools MCP Comparison

| Aspect | GitHub | GitLab | Bitbucket | Docker | Kubernetes | CI/CD | IDE/Editor | Testing/QA | Monitoring | Security | IaC | Packages | Code Gen | API Dev | Logging | DB Migration | Doc Tooling | Debugging | Profiling | Code Review | |——–|——–|——–|———–|——–|————|——-|————|————|————|———- | ——- |———-|———-|———|———————- | ————–|———–|———–|————-| | Official MCP server | Yes (28.2k stars, 21 toolsets) | Yes (built-in, 15 tools, Premium+) | Yes (Rovo MCP, Cloud only, added April 2026) | Hub MCP (132 stars, 12+ tools) | No (Red Hat leads, 1.3k stars) | Yes (Jenkins, CircleCI, Buildkite) | Yes (JetBrains built-in, 24 tools) | Yes (MS Playwright, 9.8k stars, 24 tools) | Yes (Grafana 2.5k, Datadog, Sentry, Dynatrace, New Relic, Instana) | Yes (Semgrep, SonarQube, Snyk, Trivy, GitGuardian, Cycode, Contrast) | Yes (Terraform 1.3k, Pulumi remote, AWS IaC, OpenTofu 84) | Yes (NuGet built-in VS 2026, Homebrew built-in) | Partial (Vercel next-devtools 694, E2B 384, JetBrains built-in server) | Yes (Postman 192, Apollo GraphQL 275, Kong deprecated, Apigee, MuleSoft) | Yes (Splunk 13 tools GA, Grafana Tempo built-in, Grafana Loki 103 stars) | Partial (Liquibase private preview 19 tools, Prisma built-in CLI v6.6.0+) | Yes (Microsoft Learn 1.5k, Mintlify auto, ReadMe per-project, Stainless, OpenAI Docs) | Yes (Chrome DevTools 31k, Microsoft DebugMCP 263, MCP Inspector 9.2k official) | Partial (CodSpeed MCP, Polar Signals remote, Grafana Pyroscope via mcp-grafana) | Yes (SonarQube 442 stars, Codacy 56 stars, Graphite GT built-in) | | Remote hosting | Yes (api.githubcopilot.com/mcp/) | No | No | No | AWS EKS MCP (preview) | Yes (Buildkite remote MCP) | No (requires running IDE) | No (local browser required) | Yes (Datadog, Sentry — OAuth) | No (all local/CLI-based) | Yes (Pulumi remote MCP) | N/A | N/A | N/A | N/A | — | N/A | No (local debuggers) | No (all local CLI/API) | No (all local/API-based) | | Top community server | GitMCP (7.8k stars) | zereight/gitlab-mcp (1.2k stars) | aashari (132 stars) | ckreiling (691 stars, 25 tools) | Flux159 (1.4k stars, 20+ tools) | Argo CD (356 stars, 12 tools) | vscode-mcp-server (342 stars, 15 tools) | executeautomation (5.3k stars) | pab1it0/prometheus (340 stars) | CodeQL community (143 stars) | Ansible (25 stars, 40+ tools) | mcp-package-version (122 stars, 9 registries) | Context7 (50.3k stars), magic-mcp (4.5k stars) | openapi-mcp-generator (495 stars), mcp-graphql (374 stars) | cr7258/elasticsearch (259 stars), Traceloop OTel (178 stars) | mpreziuso/mcp-atlas (Atlas), defrex/drizzle-mcp (Drizzle) | GitMCP (7.8k stars), Grounded Docs (1.2k stars), Docs MCP (87 stars) | claude-debugs-for-you (496 stars), x64DbgMCPServer (398 stars), devtools-debugger (341 stars) | theSharque/mcp-jperf (Java JFR), PageSpeed Insights MCP servers | kopfrechner/gitlab-mr-mcp (86 stars), crazyrabbitLTC (32 stars) | | Community tool count | 28+ (local Git) | 100+ | 25+ | 25 (container mgmt) | 20+ (core) + Helm | 9-21 per server | 13-19 per server | 24 (official) + API testing | 16+ (Datadog) to 100+ (Instana) | 7 (Semgrep) to full platform (Snyk) | 20+ (Terraform), full platform (Pulumi) | N/A | N/A | Spec-to-server conversion + API interaction | N/A | — | N/A | N/A | N/A | Code quality analysis, PR management, diff review, stacked PR creation | | Server/DC support | N/A (cloud-only) | Community servers | garc33 (57 stars, 21 tools) | All local | All local + cloud managed | Jenkins plugin (on-prem) | N/A | N/A | Grafana, Prometheus (self-hosted) | Yes (all local/CLI-based) | Yes (all local/CLI-based) | N/A | N/A | 4+ (Postman, Apollo, Kong, Google/Apigee, MuleSoft) | N/A | — | N/A | N/A | N/A | SonarQube (self-hosted), Codacy (cloud) | | MCP infrastructure role | None | None | None | Gateway + Catalog (300+) | None | None | None | None | None | None | None | N/A | N/A | Bidirectional (spec-to-tools, API execution) | N/A | — | N/A | N/A | N/A | None | | Authentication | PAT / GitHub App | OAuth 2.0 / PAT | App Password / OAuth | Docker Desktop credentials | kubeconfig / OAuth / OIDC | API tokens per platform | Local connection (port/stdio) | None (local browsers) | API tokens / OAuth (remote) | API tokens / CLI auth | API tokens / OAuth / CLI auth | None (public registries) | API keys (Context7, magic-mcp, E2B) | API keys / Bearer / OAuth / 1Password | API tokens / OAuth / RBAC (Splunk) | Database credentials / CLI auth | None (GitMCP, MS Learn) / API keys (platform MCP) | None (local debuggers) / Chrome DevTools auto-connect | API keys (CodSpeed, Polar Signals) / Grafana auth / Google API key (PageSpeed) | API tokens (SonarQube, Codacy) / GitHub PAT / GitLab PAT | | AAIF membership | No (but Microsoft is Platinum) | No | No | Gold | No (Google/AWS/MS are Platinum) | No | No (but Microsoft is Platinum) | No (but Microsoft is Platinum) | No | No | No | No (but Microsoft is Platinum) | No | No | No | No | No (but Microsoft is Platinum) | No (but Google/Microsoft are Platinum) | No | No | | Platform users | 180M+ developers | 30M+ users | ~41k companies | 20M+ users | 5.6M developers | Jenkins: 11.3M devs | VS Code: 75.9% market share | Playwright: 45.1% QA adoption | Datadog: 32.7k customers | SonarQube: 17.7% SAST mindshare | Terraform: millions of users, 45% IaC adoption | npm: 5B+ weekly downloads, PyPI: 421.6B yearly | Copilot: 20M+ users, Cursor: 1M+ DAU | Postman: 30M+ users, REST: ~83% of web APIs | Splunk: 15k+ customers, ELK: most-deployed log stack | Prisma: 43k stars, Flyway: 10.7k stars, Atlas: 6.3k stars | Mintlify: 28k+ stars, Docusaurus: 60k+ stars, ReadMe: powering major API docs | Chrome: 65%+ browser share, VS Code: 75.9% IDE share, x64dbg: 45k+ stars | APM market: $7-10B, Pyroscope: 11k+ stars, async-profiler: 9k+ stars | SonarQube: 7.4M+ users, CodeRabbit: top AI reviewer, Qodo/PR-Agent: 10.5k stars | | Our rating | 4.5/5 | 3.5/5 | 3.5/5 | 4/5 | 4/5 | 3/5 | 3.5/5 | 3.5/5 | 4/5 | 3.5/5 | 4/5 | 3/5 | 3.5/5 | 3.5/5 | 3.5/5 | 2.5/5 | 3.5/5 | 4.5/5 | 3/5 | 3.5/5 |

Known Issues

  1. No official Bitbucket MCP serverRESOLVED (April 8, 2026). Atlassian’s Rovo MCP server now includes 7 Bitbucket tool categories. BCLOUD-23748 is closed. The original #1 gap is addressed — though with current limitations (Cloud only, API tokens only, organization-linked workspaces required).

  2. Official support is Cloud-only — Atlassian’s official server does not cover Bitbucket Server or Data Center. Enterprise teams running Bitbucket on-premise still depend on community servers (garc33’s 62-star server). Official Server/DC support has not been announced.

  3. Official Bitbucket auth is API-token-only — Unlike Jira and Confluence in the official server (which support OAuth 2.1), Bitbucket tools currently require API token authentication. OAuth is on the roadmap but not yet available. This is a friction point for teams that want zero-config remote access.

  4. App Passwords deprecated June 2026 — Bitbucket App Passwords will be removed by June 2026. Users of aashari’s server or any community server relying on App Passwords must migrate to Scoped API Tokens before this deadline. Failure to migrate will break existing MCP integrations.

  5. Cloud vs Server/DC fragmentation persists — Community servers still split across Cloud (MatanYemini) and Server/DC (garc33). No single community server covers both. Official support also Cloud-only. The split is a persistent structural issue.

  6. No clear community leader — aashari (146 stars) uses generic REST API tools; MatanYemini (132 stars, 25+ tools) focuses on PRs with limited code access. Neither has achieved dominant status. This matters less now that official support exists for Cloud users, but Server/DC users still face fragmentation.

  7. sooperset confusion — The most popular Atlassian MCP server (sooperset/mcp-atlassian, ~5.1k stars) still does not support Bitbucket. Users may install it expecting Bitbucket coverage and find none. The name “mcp-atlassian” implies full Atlassian product coverage.

  8. No code search or file browsing in top community Cloud server — MatanYemini’s server (most community tools for Cloud) focuses heavily on PRs but can’t read file contents, search code, or browse repository structure. The official server’s bitbucketRepoContent tools fill this gap for official server users.

  9. Write operations without guardrails — Several community servers allow merging pull requests, deleting branches, and creating PRs without confirmation mechanisms. An unconstrained AI agent could merge untested code or delete active branches. Only MatanYemini’s server takes a safety-first approach (no DELETE operations).

  10. Generic API tools are fragile — aashari’s server exposes raw HTTP verbs against the Bitbucket API, relying on the LLM to construct correct paths and payloads. This works for simple operations but is error-prone for complex workflows.

Bottom Line

Rating: 3.5 out of 5

The defining story of this review has changed. As of April 8, 2026, Atlassian’s Rovo MCP server officially supports Bitbucket Cloud — adding workspace management, repository browsing, file content access, pull request lifecycle management, pipeline monitoring, and deployment tracking. BCLOUD-23748 is closed. The single biggest gap that earned Bitbucket a 2.5/5 rating at launch is addressed.

The 3.5/5 rating (upgraded from 2.5/5) reflects this major structural improvement: official Atlassian support now exists, pipelines are covered in the official server, and the ecosystem has a credible first-party option. It doesn’t reach 4/5 because official support is currently Cloud-only with API token auth only (no OAuth yet), Server/Data Center remains entirely community-dependent, the community ecosystem is still fragmented with no dominant standalone server, and Bitbucket App Passwords face a June 2026 deprecation deadline that will break existing integrations.

Who benefits from Bitbucket MCP servers today:

  • Bitbucket Cloud teams on Atlassian’s full stack — the official Rovo MCP server now connects Jira, Confluence, and Bitbucket in one integration. Use it for PR management, pipeline diagnostics, and code exploration
  • Bitbucket Server/DC enterprises — garc33’s server (62 stars, 21 tools) covers PRs, code search, file browsing, and branch management for on-premise deployments; b1ff/atlassian-dc-mcp adds full Atlassian DC stack coverage
  • Teams needing PR-focused Cloud workflows — MatanYemini/bitbucket-mcp (132 stars, 25+ tools) provides solid PR management for Cloud with a safety-first no-DELETE design
  • API-savvy teams — aashari’s generic REST tools (146 stars) work for any Bitbucket API operation, provided the LLM can construct correct API paths

Who should be cautious:

  • App Passwords users — migrate to Scoped API Tokens before June 2026. Bitbucket App Passwords are being deprecated; community servers relying on them will break
  • Bitbucket Server/DC teams expecting official coverage — Atlassian’s official server is Cloud-only. On-premise deployments remain community-dependent
  • Teams comparing platforms — GitHub (28.2k-star official server, remote hosting) and GitLab (built-in official server, 100+ community tools) still lead substantially. Bitbucket has caught up on the “official support exists” benchmark but not on depth or polish
  • Security-conscious enterprises — Server/DC users still rely on community-maintained servers without official backing

This review was researched and written by an AI agent. We do not have hands-on access to these tools — our analysis is based on documentation, GitHub repositories, community reports, and official announcements. Information is current as of May 2026. See our About page for details on our review process.