What can @nexus2520/bitbucket-mcp-server do?

bitbucket cloud and server api abstraction layer, pull request inspection and metadata extraction, repository browsing and file tree navigation, commit history and diff retrieval, branch and tag management operations, mcp protocol request routing and authentication handling

@nexus2520/bitbucket-mcp-server

MCP ServerFree

MCP server for Bitbucket API integration - supports both Cloud and Server

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

bitbucket cloud and server api abstraction layer

Medium confidence

Provides unified MCP protocol interface to both Bitbucket Cloud (REST API v2.0) and Bitbucket Server (REST API 1.0) backends through a single server implementation. Routes requests to appropriate API endpoint based on configured instance type, handling authentication differences (OAuth2 for Cloud, Basic/Token for Server) and API response normalization across versions.

Solves for

Connect Claude or other MCP clients to both Bitbucket Cloud and self-hosted Bitbucket Server instances without maintaining separate integrationsAbstract away Bitbucket API version differences so AI agents can work with repositories regardless of deployment modelEnable programmatic access to Bitbucket repositories and metadata from LLM-based tools without direct REST API calls

Best for

Teams using both Bitbucket Cloud and self-hosted Server instances who need unified AI tooling

Enterprise developers building LLM agents that need to interact with Bitbucket across multiple deployment models

Organizations migrating from Server to Cloud who need backward compatibility during transition

Requires

Node.js 16+ for MCP server runtime

Bitbucket Cloud workspace with OAuth2 app credentials OR Bitbucket Server instance with API token/Basic auth

MCP client implementation (Claude Desktop, custom agent framework, etc.)

Limitations

API feature parity gaps between Cloud v2.0 and Server 1.0 may require conditional logic for certain operations

Authentication setup requires separate credentials for each Bitbucket instance (no cross-instance SSO)

Response normalization adds abstraction overhead — some Cloud-specific or Server-specific fields may be lost in translation

What makes it unique

Dual-backend MCP server supporting both Bitbucket Cloud and Server with unified interface — most MCP Bitbucket implementations only target Cloud, requiring separate tooling for Server instances

vs alternatives

Eliminates need for separate MCP servers or custom adapters when working with mixed Bitbucket deployments, reducing integration complexity for enterprises with hybrid infrastructure

pull request inspection and metadata extraction

Medium confidence

Retrieves comprehensive pull request data including title, description, source/target branches, author, reviewers, approval status, and commit history through MCP tool calls. Implements pagination for large PR lists and normalizes response structure across Bitbucket Cloud and Server API versions to present consistent metadata regardless of backend.

Solves for

Fetch detailed PR information to provide context for code review automation or AI-assisted analysisList open or merged pull requests in a repository to track code changes and review statusExtract PR metadata (reviewers, approval status, branch info) for workflow automation or reporting

Best for

AI code review agents that need to analyze PR context before generating feedback

Developers building Bitbucket-integrated LLM workflows for change tracking and approval automation

Teams automating PR triage, assignment, or status reporting through AI agents

Requires

Valid Bitbucket repository identifier (workspace/project and repo slug)

Read access to target repository (implicit in authentication credentials)

MCP client capable of handling paginated responses or implementing pagination loops

Limitations

Pagination requires multiple requests for repositories with hundreds of open PRs — no built-in streaming or cursor-based continuation

PR diff content not included in metadata extraction — requires separate diff retrieval capability

Approval status representation differs between Cloud (reviewers array with status) and Server (approval count) — normalization may lose granularity

What makes it unique

Normalizes PR metadata across Bitbucket Cloud and Server APIs, handling structural differences in approval workflows and reviewer representation without exposing backend-specific quirks to the MCP client

vs alternatives

Provides consistent PR data structure for AI agents regardless of Bitbucket deployment, whereas direct API calls require conditional logic to handle Cloud vs Server response formats

repository browsing and file tree navigation

Medium confidence

Enables traversal of repository directory structure and retrieval of file contents through MCP tools that map to Bitbucket's source API endpoints. Supports branch/tag selection, recursive directory listing with pagination, and file content retrieval with encoding handling. Implements caching or lazy-loading patterns to avoid excessive API calls when exploring large codebases.

Solves for

Navigate repository structure to understand codebase organization before generating code or reviewsRetrieve specific file contents for analysis, context injection into LLM prompts, or code generation tasksList directory contents to discover relevant files for a given task (e.g., finding test files, config files)

Best for

LLM agents performing code analysis or generation that need to explore repository structure

Developers building AI-assisted code navigation or documentation generation tools

Teams automating codebase discovery tasks (finding dependencies, configuration, test coverage)

Requires

Read access to target repository

Valid branch or tag reference (defaults to main/master if not specified)

MCP client with ability to make sequential requests for directory traversal

Limitations

Large repositories with deep directory trees may require many API calls — no built-in recursive tree snapshot or tarball export

File size limits may apply (Bitbucket typically limits responses to reasonable sizes) — very large files may need chunked retrieval

Binary file handling not specified — may return encoding errors or require special handling for non-text files

What makes it unique

Abstracts Bitbucket Cloud and Server source API differences to provide unified file browsing interface — handles different endpoint structures and response formats transparently

vs alternatives

Single MCP tool set works across both Bitbucket deployments without client-side branching logic, whereas direct API integration requires separate code paths for Cloud vs Server file retrieval

commit history and diff retrieval

Medium confidence

Fetches commit logs with metadata (author, timestamp, message, parent commits) and retrieves diffs between commits or branches through MCP tools. Implements pagination for large commit histories and supports filtering by author, date range, or file path. Normalizes diff format across Bitbucket versions and handles merge commits appropriately.

Solves for

Retrieve commit history to understand code evolution and change patterns for analysis or documentationFetch diffs between commits or branches to provide code change context for review or analysis tasksFilter commits by author or date to track specific developer contributions or time-based changes

Best for

AI code review agents that need to analyze what changed and why in a PR or commit range

Developers building code archaeology or blame-tracking tools powered by LLMs

Teams automating changelog generation or commit message analysis

Requires

Read access to target repository

Valid branch or commit SHA references

MCP client capable of handling potentially large diff payloads

Limitations

Large diffs (many files or large file changes) may exceed API response size limits — requires chunking or pagination

Merge commits may have multiple parents — diff representation may be ambiguous without explicit merge-base specification

Commit filtering by file path not universally supported across Cloud and Server — may require client-side filtering

What makes it unique

Normalizes commit and diff APIs across Bitbucket Cloud and Server, handling differences in pagination, merge commit representation, and diff formatting without exposing backend-specific details

vs alternatives

Provides unified commit history and diff interface for AI agents across both Bitbucket deployments, whereas separate integrations would require duplicate logic for Cloud and Server API differences

branch and tag management operations

Medium confidence

Provides MCP tools to list branches and tags, retrieve branch metadata (last commit, protection status), and potentially create/delete branches through Bitbucket API calls. Implements filtering and sorting for large branch lists and normalizes branch protection rules representation across Cloud and Server versions.

Solves for

List available branches and tags to understand repository structure and release historyCheck branch protection status before attempting automated changes or mergesCreate feature branches programmatically as part of AI-assisted development workflows

Best for

LLM agents managing branching workflows or automated PR creation

Teams building AI-assisted release management or branch governance tools

Developers automating branch discovery for deployment or testing pipelines

Requires

Read access to target repository (list operations)

Write access for branch creation/deletion operations

Valid repository identifiers

Limitations

Branch protection rules representation differs significantly between Cloud and Server — normalization may lose specific rule details

Create/delete branch operations require write access — may not be available in read-only integration scenarios

Large repositories with hundreds of branches may require pagination — no built-in branch filtering by pattern

What makes it unique

Abstracts branch protection rule differences between Bitbucket Cloud (branch permissions, merge checks) and Server (branch permissions, hooks) into unified interface

vs alternatives

Single MCP tool set handles branch operations across both Bitbucket deployments without client-side version detection, whereas direct API calls require conditional logic for Cloud vs Server branch protection APIs

mcp protocol request routing and authentication handling

Medium confidence

Core MCP server implementation that routes incoming tool calls to appropriate Bitbucket API endpoints based on configured instance type (Cloud vs Server). Manages authentication state (OAuth2 tokens for Cloud, Basic/Token auth for Server), handles token refresh, and implements error handling with MCP-compliant error responses. Includes request validation and parameter marshaling.

Solves for

Enable MCP clients (Claude, custom agents) to transparently call Bitbucket operations without managing authentication or API routingAbstract authentication complexity so clients don't need to handle OAuth2 flows or token managementProvide consistent error handling and response formatting across all Bitbucket operations

Best for

Developers integrating Bitbucket with Claude or other MCP-compatible AI agents

Teams building custom LLM agent frameworks that need Bitbucket access

Organizations standardizing on MCP for tool integration across their AI infrastructure

Requires

Node.js 16+ runtime

Bitbucket Cloud OAuth2 credentials (client ID, secret, refresh token) OR Bitbucket Server API token/Basic auth credentials

MCP client implementation with tool calling support

Limitations

Authentication credentials must be provided at server startup — no dynamic credential rotation or per-request auth override

OAuth2 token refresh for Cloud may require periodic server restart if tokens expire during long-running operations

MCP protocol overhead adds latency compared to direct API calls — each operation requires MCP serialization/deserialization

What makes it unique

Implements dual-backend MCP server with unified authentication abstraction — single server instance handles both Cloud OAuth2 and Server token/Basic auth without client-side branching

vs alternatives

Eliminates need for separate MCP servers or complex client-side authentication logic when working with mixed Bitbucket deployments, providing single integration point for both Cloud and Server

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @nexus2520/bitbucket-mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server28

GitHub Repos Manager MCP Server

** - Token-based GitHub automation management. No Docker, Flexible configuration, 80+ tools with direct API integration.

repository metadata and search operations with filteringpull request creation, review, and file analysisfile management with create, update, upload, and delete operationsrepository search and discovery with advanced filtering

4 shared capabilities

MCP Server42

octocode-mcp

MCP server for semantic code research and context generation on real-time using LLM patterns | Search naturally across public & private repos based on your permissions | Transform any accessible codebase/s into AI-optimized knowledge on simple and complex flows | Find real implementations and live d

repository structure visualization and navigationfile content retrieval with caching and streaming

2 shared capabilities

MCP Server25

Gitee

** - Gitee API integration, repository, issue, and pull request management, and more.

file content retrieval and repository browsingrepository discovery and metadata retrieval with search

2 shared capabilities

MCP Server28

Harness

** - Access and interact with Harness platform data, including pipelines, repositories, logs, and artifact registries.

repository browsing and file retrieval with connector abstraction

1 shared capability

MCP Server24

GitLab

** - GitLab API, enabling project management.

gitlab repository file and directory browsing

1 shared capability

Extension46

GitLab

Official GitLab-maintained extension for Visual Studio Code.

repository browsing and code navigation without cloning

1 shared capability

Best For

✓Teams using both Bitbucket Cloud and self-hosted Server instances who need unified AI tooling
✓Enterprise developers building LLM agents that need to interact with Bitbucket across multiple deployment models
✓Organizations migrating from Server to Cloud who need backward compatibility during transition
✓AI code review agents that need to analyze PR context before generating feedback
✓Developers building Bitbucket-integrated LLM workflows for change tracking and approval automation
✓Teams automating PR triage, assignment, or status reporting through AI agents
✓LLM agents performing code analysis or generation that need to explore repository structure
✓Developers building AI-assisted code navigation or documentation generation tools

Known Limitations

⚠API feature parity gaps between Cloud v2.0 and Server 1.0 may require conditional logic for certain operations
⚠Authentication setup requires separate credentials for each Bitbucket instance (no cross-instance SSO)
⚠Response normalization adds abstraction overhead — some Cloud-specific or Server-specific fields may be lost in translation
⚠Pagination requires multiple requests for repositories with hundreds of open PRs — no built-in streaming or cursor-based continuation
⚠PR diff content not included in metadata extraction — requires separate diff retrieval capability
⚠Approval status representation differs between Cloud (reviewers array with status) and Server (approval count) — normalization may lose granularity

Requirements

Node.js 16+ for MCP server runtimeBitbucket Cloud workspace with OAuth2 app credentials OR Bitbucket Server instance with API token/Basic authMCP client implementation (Claude Desktop, custom agent framework, etc.)Network access to Bitbucket Cloud API (api.bitbucket.org) or self-hosted Server instanceValid Bitbucket repository identifier (workspace/project and repo slug)Read access to target repository (implicit in authentication credentials)MCP client capable of handling paginated responses or implementing pagination loopsRead access to target repository

Input / Output

Accepts: MCP tool call requests with repository identifiers, branch names, commit SHAs, Configuration objects specifying Bitbucket instance type and authentication credentials, Repository identifiers (workspace/project, repository slug), Optional filters: PR state (open/merged/declined), author, reviewer, Pagination parameters (limit, offset/page), Repository identifiers and branch/tag name, File or directory path within repository, Optional pagination parameters for large directories, Repository identifiers, branch names, or commit SHAs, Optional filters: author email, date range, file path patterns, Pagination parameters for commit lists, Repository identifiers, Optional branch name patterns or filters, Pagination parameters for large branch lists, MCP tool call requests with structured parameters, Configuration environment variables or config files with authentication credentials

Produces: Structured JSON responses containing repository metadata, commit history, pull request details, Normalized API responses mapped to common schema across Cloud and Server variants, Structured JSON array of pull request objects with metadata, Individual PR detail objects containing full context (description, reviewers, commit list), Directory listing with file metadata (name, type, size, last commit), Raw file contents as text or base64-encoded binary, Structured tree representation for directory hierarchies, Structured commit objects with metadata (hash, author, timestamp, message, parent SHAs), Unified diff format showing additions/deletions across files, Paginated commit history arrays, Structured branch objects with metadata (name, last commit SHA, protection status), Tag objects with version information and commit references, Success/failure responses for create/delete operations, MCP tool result responses with structured data, MCP error responses with error codes and messages

UnfragileRank

Adoption15%(25% weight)

Quality14%(25% weight)

Ecosystem50%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit @nexus2520/bitbucket-mcp-server→

Package Details

npm

Registry

2.0.4

Version

Weekly Downloads

About

MCP server for Bitbucket API integration - supports both Cloud and Server

Alternatives to @nexus2520/bitbucket-mcp-server

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @nexus2520/bitbucket-mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities6 decomposed

bitbucket cloud and server api abstraction layer

Medium confidence

Solves for

Best for

Teams using both Bitbucket Cloud and self-hosted Server instances who need unified AI tooling

Enterprise developers building LLM agents that need to interact with Bitbucket across multiple deployment models

Organizations migrating from Server to Cloud who need backward compatibility during transition

Requires

Node.js 16+ for MCP server runtime

Bitbucket Cloud workspace with OAuth2 app credentials OR Bitbucket Server instance with API token/Basic auth

MCP client implementation (Claude Desktop, custom agent framework, etc.)

Limitations

API feature parity gaps between Cloud v2.0 and Server 1.0 may require conditional logic for certain operations

Authentication setup requires separate credentials for each Bitbucket instance (no cross-instance SSO)

Response normalization adds abstraction overhead — some Cloud-specific or Server-specific fields may be lost in translation

What makes it unique

Dual-backend MCP server supporting both Bitbucket Cloud and Server with unified interface — most MCP Bitbucket implementations only target Cloud, requiring separate tooling for Server instances

vs alternatives

Eliminates need for separate MCP servers or custom adapters when working with mixed Bitbucket deployments, reducing integration complexity for enterprises with hybrid infrastructure

pull request inspection and metadata extraction

Medium confidence

Solves for

Best for

AI code review agents that need to analyze PR context before generating feedback

Developers building Bitbucket-integrated LLM workflows for change tracking and approval automation

Teams automating PR triage, assignment, or status reporting through AI agents

Requires

Valid Bitbucket repository identifier (workspace/project and repo slug)

Read access to target repository (implicit in authentication credentials)

MCP client capable of handling paginated responses or implementing pagination loops

Limitations

Pagination requires multiple requests for repositories with hundreds of open PRs — no built-in streaming or cursor-based continuation

PR diff content not included in metadata extraction — requires separate diff retrieval capability

Approval status representation differs between Cloud (reviewers array with status) and Server (approval count) — normalization may lose granularity

What makes it unique

vs alternatives

Provides consistent PR data structure for AI agents regardless of Bitbucket deployment, whereas direct API calls require conditional logic to handle Cloud vs Server response formats

repository browsing and file tree navigation

Medium confidence

Solves for

Best for

LLM agents performing code analysis or generation that need to explore repository structure

Developers building AI-assisted code navigation or documentation generation tools

Teams automating codebase discovery tasks (finding dependencies, configuration, test coverage)

Requires

Read access to target repository

Valid branch or tag reference (defaults to main/master if not specified)

MCP client with ability to make sequential requests for directory traversal

Limitations

Large repositories with deep directory trees may require many API calls — no built-in recursive tree snapshot or tarball export

File size limits may apply (Bitbucket typically limits responses to reasonable sizes) — very large files may need chunked retrieval

Binary file handling not specified — may return encoding errors or require special handling for non-text files

What makes it unique

Abstracts Bitbucket Cloud and Server source API differences to provide unified file browsing interface — handles different endpoint structures and response formats transparently

vs alternatives

Single MCP tool set works across both Bitbucket deployments without client-side branching logic, whereas direct API integration requires separate code paths for Cloud vs Server file retrieval

commit history and diff retrieval

Medium confidence

Solves for

Best for

AI code review agents that need to analyze what changed and why in a PR or commit range

Developers building code archaeology or blame-tracking tools powered by LLMs

Teams automating changelog generation or commit message analysis

Requires

Read access to target repository

Valid branch or commit SHA references

MCP client capable of handling potentially large diff payloads

Limitations

Large diffs (many files or large file changes) may exceed API response size limits — requires chunking or pagination

Merge commits may have multiple parents — diff representation may be ambiguous without explicit merge-base specification

Commit filtering by file path not universally supported across Cloud and Server — may require client-side filtering

What makes it unique

Normalizes commit and diff APIs across Bitbucket Cloud and Server, handling differences in pagination, merge commit representation, and diff formatting without exposing backend-specific details

vs alternatives

Provides unified commit history and diff interface for AI agents across both Bitbucket deployments, whereas separate integrations would require duplicate logic for Cloud and Server API differences

branch and tag management operations

Medium confidence

Solves for

Best for

LLM agents managing branching workflows or automated PR creation

Teams building AI-assisted release management or branch governance tools

Developers automating branch discovery for deployment or testing pipelines

Requires

Read access to target repository (list operations)

Write access for branch creation/deletion operations

Valid repository identifiers

Limitations

Branch protection rules representation differs significantly between Cloud and Server — normalization may lose specific rule details

Create/delete branch operations require write access — may not be available in read-only integration scenarios

Large repositories with hundreds of branches may require pagination — no built-in branch filtering by pattern

What makes it unique

Abstracts branch protection rule differences between Bitbucket Cloud (branch permissions, merge checks) and Server (branch permissions, hooks) into unified interface

vs alternatives

mcp protocol request routing and authentication handling

Medium confidence

Solves for

Best for

Developers integrating Bitbucket with Claude or other MCP-compatible AI agents

Teams building custom LLM agent frameworks that need Bitbucket access

Organizations standardizing on MCP for tool integration across their AI infrastructure

Requires

Node.js 16+ runtime

Bitbucket Cloud OAuth2 credentials (client ID, secret, refresh token) OR Bitbucket Server API token/Basic auth credentials

MCP client implementation with tool calling support

Limitations

Authentication credentials must be provided at server startup — no dynamic credential rotation or per-request auth override

OAuth2 token refresh for Cloud may require periodic server restart if tokens expire during long-running operations

MCP protocol overhead adds latency compared to direct API calls — each operation requires MCP serialization/deserialization

What makes it unique

Implements dual-backend MCP server with unified authentication abstraction — single server instance handles both Cloud OAuth2 and Server token/Basic auth without client-side branching

vs alternatives

Eliminates need for separate MCP servers or complex client-side authentication logic when working with mixed Bitbucket deployments, providing single integration point for both Cloud and Server

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @nexus2520/bitbucket-mcp-server

IntelliCode46Extension

AI-assisted development

Compare →

GitHub Copilot Chat49Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot48Extension

Your AI pair programmer

Compare →

Claude Code for VS Code48Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@nexus2520/bitbucket-mcp-server

Capabilities6 decomposed

bitbucket cloud and server api abstraction layer

pull request inspection and metadata extraction

repository browsing and file tree navigation

commit history and diff retrieval

branch and tag management operations

mcp protocol request routing and authentication handling

Related Artifactssharing capabilities

GitHub Repos Manager MCP Server

octocode-mcp

Gitee

Harness

GitLab

GitLab

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @nexus2520/bitbucket-mcp-server

Are you the builder of @nexus2520/bitbucket-mcp-server?

Get the weekly brief

Data Sources

@nexus2520/bitbucket-mcp-server

Capabilities6 decomposed

bitbucket cloud and server api abstraction layer

pull request inspection and metadata extraction

repository browsing and file tree navigation

commit history and diff retrieval

branch and tag management operations

mcp protocol request routing and authentication handling

Related Artifactssharing capabilities

GitHub Repos Manager MCP Server

octocode-mcp

Gitee

Harness

GitLab

GitLab

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @nexus2520/bitbucket-mcp-server

Are you the builder of @nexus2520/bitbucket-mcp-server?

Get the weekly brief

Data Sources