| FMRS | 56 / 100 · C | 80 / 100 · B | 79 / 100 · B |
|---|
| Reliability | 7 / 20 | 14 / 20 | 12 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 15 / 20 |
|---|
| Best for | - Teams running self-hosted Bitbucket Server / Data Center who want a conversational interface for PR workflows
- CI/CD or proxy environments that need safe, read-only access to Bitbucket data
- Organizations behind Zero Trust networks that need custom headers to reach Bitbucket
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users on Bitbucket Cloud (bitbucket.org) rather than Bitbucket Server/Data Center, since this server targets the Server API
- Users unwilling to run a local Node.js MCP server process
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Requires a Bitbucket Server personal access token, or username/password basic-auth credentials
- The scope of allowed operations is bounded by the configured credential's repository permissions; write actions (create/merge/comment/delete branch, etc.) need corresponding write access
- Optional custom HTTP headers are sent with every request and may carry sensitive tokens that must be managed carefully
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Authentication tokens or passwords are configured as plaintext environment variables and must be stored/transmitted securely
- Outside read-only mode, the model can directly merge, decline, delete branches, and delete comments — irreversible or collaboration-impacting actions with real misuse potential
- The log file is written to local disk by default (`~/.bitbucket-server-mcp/bitbucket.log`) and may capture sensitive operation details
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Desktop, VS Code | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 27 | 2 | 19 |
|---|