| FMRS | 56 / 100 · C | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 7 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 11 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 18 / 20 | 14 / 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
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| 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)
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| 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
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| 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
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, VS Code | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 27 | 2 | 15 |
|---|