Skip to content

Security & Limitations

FeatureDetails
Read-only by designNo write, delete, or modify operations exist at any layer of the codebase
Runtime protectionmakeRequest() in src/api.ts actively blocks any non-GET HTTP request — not just absent from the API
Safe for productionNo destructive actions are supported, making the server safe to connect to production Bitbucket workspaces
Authenticated accessAll requests require a valid API token — no anonymous access to private repositories
Type-safe inputsAll tool parameters are validated with Zod schemas before reaching handler code
Branch name supportBranch names with special characters (e.g., feature/SSP-1024) are correctly handled
Dynamic commit resolutionBranch names are automatically resolved to commit SHAs for subdirectory browsing — prevents path traversal edge cases
Context-aware errorsError messages include actionable suggestions (e.g., enabling code search when bb_search_code fails)
LimitationDetails
⚠️Rate limitingSubject to Bitbucket Cloud API rate limits. The server does not implement custom throttling or request queuing.
⚠️Code search requirementbb_search_code requires code search to be manually enabled in Bitbucket account settings at bitbucket.org/search
⚠️File size limitsLarge files are handled with pagination — up to 10,000 lines per request via bb_get_file_content
⚠️Bitbucket Cloud onlyThe server targets Bitbucket Cloud (bitbucket.org) API v2.0. Bitbucket Server (on-premises) is not supported.
⚠️6 tools not integration-tested31 of 37 tools are verified against real API endpoints. The remaining 6 use the same patterns but rely on unit test coverage.
  • Store BITBUCKET_API_TOKEN and BITBUCKET_EMAIL only in your MCP client config file — never hard-code them in source files
  • Add .vscode/mcp.json and .cursor/mcp.json to .gitignore if they contain real credentials
  • Use API tokens with minimal required scope (Read only, Bitbucket app only)
  • Set token expiry dates when creating API tokens in the Atlassian portal
  • Rotate API tokens regularly

Report security vulnerabilities via GitHub Issues or directly to the maintainer.