Git Summary vs Atlassian Dc MCP Bitbucket
A side-by-side look at the Git Summary and Atlassian Dc MCP Bitbucket MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git Summary for version control work as a local process; choose Atlassian Dc MCP Bitbucket for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git Summary when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
git_summary, git_changes, git_blame.
Choose Atlassian Dc MCP Bitbucket when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BITBUCKET_HOST, BITBUCKET_API_BASE_PATH, BITBUCKET_API_TOKEN, BITBUCKET_DEFAULT_PAGE_SIZE, ATLASSIAN_DC_MCP_CONFIG_FILE, ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 55/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | BITBUCKET_HOSTBITBUCKET_API_BASE_PATHBITBUCKET_API_TOKENBITBUCKET_DEFAULT_PAGE_SIZEATLASSIAN_DC_MCP_CONFIG_FILEATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 105 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Git Summary | View Atlassian Dc MCP Bitbucket |
Tools & capabilities
Git Summary tools 6
git_summaryGet a structured overview of a Git repository: current branch, recent commits, contributors, and repo stats. Works on any local Git repo.git_changesGet a summary of changes in a commit range: what files changed, who changed them, and a diff stat. Useful for understanding what happened between two points in history.git_blameAnalyze who wrote each line of a file, when, and in which commit. Get top contributors and ownership breakdown. Optionally limit to a line range.git_changelogAuto-generate a changelog from Git commits. Groups commits by type (feat, fix, docs, etc.) using conventional commit format. Specify a range or get the full log.git_branch_healthAnalyze all local branches: find stale branches, merged branches ready for cleanup, and branches that are ahead/behind. Helps keep your repo tidy.git_searchSearch through Git history for commits matching a query. Searches both commit messages and code changes (pickaxe search). Find when a change was introduced or a bug was created.
Atlassian Dc MCP Bitbucket tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Git Summary
{
"mcpServers": {
"git-summary": {
"command": "npx",
"args": [
"-y",
"git-summary-mcp"
]
}
}
}
Atlassian Dc MCP Bitbucket
{
"mcpServers": {
"atlassian-dc-mcp-bitbucket-2": {
"command": "npx",
"args": [
"-y",
"@atlassian-dc-mcp/jira"
],
"env": {
"BITBUCKET_HOST": "YOUR_BITBUCKET_HOST_HERE",
"BITBUCKET_API_BASE_PATH": "YOUR_BITBUCKET_API_BASE_PATH_HERE",
"BITBUCKET_API_TOKEN": "YOUR_BITBUCKET_API_TOKEN_HERE",
"BITBUCKET_DEFAULT_PAGE_SIZE": "YOUR_BITBUCKET_DEFAULT_PAGE_SIZE_HERE",
"ATLASSIAN_DC_MCP_CONFIG_FILE": "YOUR_ATLASSIAN_DC_MCP_CONFIG_FILE_HERE",
"ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS": "YOUR_ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS_HERE"
}
}
}
}
Frequently asked questions
Git Summary is categorized under Version Control and uses a local stdio subprocess. Atlassian Dc MCP Bitbucket belongs to Version Control and uses a local stdio subprocess. Pick Git Summary for version control work and Atlassian Dc MCP Bitbucket for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Git Summary has no declared pricing — check the project's own site. Atlassian Dc MCP Bitbucket has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add git-summary and atlassian-dc-mcp-bitbucket-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git Summary has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Atlassian Dc MCP Bitbucket has 51/100 (Good) with 1 views, 0 installs and 105 GitHub stars.