{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-nexus2520bitbucket-mcp-server","slug":"npm-nexus2520bitbucket-mcp-server","name":"@nexus2520/bitbucket-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@nexus2520/bitbucket-mcp-server","page_url":"https://unfragile.ai/npm-nexus2520bitbucket-mcp-server","categories":["mcp-servers"],"tags":["mcp","bitbucket","api","model-context-protocol","bitbucket-server","bitbucket-cloud","pull-request","code-review"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-nexus2520bitbucket-mcp-server__cap_0","uri":"capability://tool.use.integration.bitbucket.cloud.and.server.api.abstraction.layer","name":"bitbucket cloud and server api abstraction layer","description":"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.","intents":["Connect Claude or other MCP clients to both Bitbucket Cloud and self-hosted Bitbucket Server instances without maintaining separate integrations","Abstract away Bitbucket API version differences so AI agents can work with repositories regardless of deployment model","Enable 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"],"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"],"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.)","Network access to Bitbucket Cloud API (api.bitbucket.org) or self-hosted Server instance"],"input_types":["MCP tool call requests with repository identifiers, branch names, commit SHAs","Configuration objects specifying Bitbucket instance type and authentication credentials"],"output_types":["Structured JSON responses containing repository metadata, commit history, pull request details","Normalized API responses mapped to common schema across Cloud and Server variants"],"categories":["tool-use-integration","api-abstraction"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nexus2520bitbucket-mcp-server__cap_1","uri":"capability://tool.use.integration.pull.request.inspection.and.metadata.extraction","name":"pull request inspection and metadata extraction","description":"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.","intents":["Fetch detailed PR information to provide context for code review automation or AI-assisted analysis","List open or merged pull requests in a repository to track code changes and review status","Extract 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"],"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"],"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"],"input_types":["Repository identifiers (workspace/project, repository slug)","Optional filters: PR state (open/merged/declined), author, reviewer","Pagination parameters (limit, offset/page)"],"output_types":["Structured JSON array of pull request objects with metadata","Individual PR detail objects containing full context (description, reviewers, commit list)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nexus2520bitbucket-mcp-server__cap_2","uri":"capability://tool.use.integration.repository.browsing.and.file.tree.navigation","name":"repository browsing and file tree navigation","description":"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.","intents":["Navigate repository structure to understand codebase organization before generating code or reviews","Retrieve specific file contents for analysis, context injection into LLM prompts, or code generation tasks","List 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)"],"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"],"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"],"input_types":["Repository identifiers and branch/tag name","File or directory path within repository","Optional pagination parameters for large directories"],"output_types":["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"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nexus2520bitbucket-mcp-server__cap_3","uri":"capability://tool.use.integration.commit.history.and.diff.retrieval","name":"commit history and diff retrieval","description":"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.","intents":["Retrieve commit history to understand code evolution and change patterns for analysis or documentation","Fetch diffs between commits or branches to provide code change context for review or analysis tasks","Filter 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"],"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"],"requires":["Read access to target repository","Valid branch or commit SHA references","MCP client capable of handling potentially large diff payloads"],"input_types":["Repository identifiers, branch names, or commit SHAs","Optional filters: author email, date range, file path patterns","Pagination parameters for commit lists"],"output_types":["Structured commit objects with metadata (hash, author, timestamp, message, parent SHAs)","Unified diff format showing additions/deletions across files","Paginated commit history arrays"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nexus2520bitbucket-mcp-server__cap_4","uri":"capability://tool.use.integration.branch.and.tag.management.operations","name":"branch and tag management operations","description":"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.","intents":["List available branches and tags to understand repository structure and release history","Check branch protection status before attempting automated changes or merges","Create 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"],"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"],"requires":["Read access to target repository (list operations)","Write access for branch creation/deletion operations","Valid repository identifiers"],"input_types":["Repository identifiers","Optional branch name patterns or filters","Pagination parameters for large branch lists"],"output_types":["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"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-nexus2520bitbucket-mcp-server__cap_5","uri":"capability://tool.use.integration.mcp.protocol.request.routing.and.authentication.handling","name":"mcp protocol request routing and authentication handling","description":"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.","intents":["Enable MCP clients (Claude, custom agents) to transparently call Bitbucket operations without managing authentication or API routing","Abstract authentication complexity so clients don't need to handle OAuth2 flows or token management","Provide 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"],"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"],"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","Network connectivity to Bitbucket Cloud or Server instance"],"input_types":["MCP tool call requests with structured parameters","Configuration environment variables or config files with authentication credentials"],"output_types":["MCP tool result responses with structured data","MCP error responses with error codes and messages"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["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.)","Network access to Bitbucket Cloud API (api.bitbucket.org) or self-hosted Server instance","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","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"],"failure_modes":["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","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","Large diffs (many files or large file changes) may exceed API response size limits — requires chunking or pagination","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.5000000000000001,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.904Z","last_scraped_at":"2026-05-03T14:23:36.026Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-nexus2520bitbucket-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-nexus2520bitbucket-mcp-server"}},"signature":"OQnccjR4vztFplqdkfrFBUqw5EZq4BOK5C76c9hMGAzh/Vr9WXpjvaIIB55uXa830BF0nUSLwx02y8hUoDNZCg==","signedAt":"2026-06-22T14:00:07.544Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-nexus2520bitbucket-mcp-server","artifact":"https://unfragile.ai/npm-nexus2520bitbucket-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-nexus2520bitbucket-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}