Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
Selects the minimum code context an LLM needs to understand a git diff: graph-based fragment selection under a token budget, deterministic, 30+ languages. Published on PyPI and in the MCP Registry.
Bitbucket Cloud CLI and MCP server. Manages workspaces, repos, PRs, pipelines, issues, and source code. Token introspection hides tools the API key can't use.
Quality signal
41/100 (Fair)
41/100 (Fair)
Install path
uvx · high
Remote · high
Engagement
0 0 0 2
1 0 0 4
Tools
Not listed yet
Dual mode: interactive CLI and MCP server for AI integrationGit-aware context auto-detection from .git/configMulti-profile support with automatic profile selectionSupports Atlassian API tokens with scoped permissionsOAuth 2.0 authentication with automatic token refreshScope-aware MCP server hides unauthorized tools