Atlassian Dc MCP Bitbucket vs Git Summary
A side-by-side look at the Atlassian Dc MCP Bitbucket and Git Summary MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Atlassian Dc MCP Bitbucket for version control work as a local process; choose Git Summary 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 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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 51/100 · Good | 55/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 | BITBUCKET_HOSTBITBUCKET_API_BASE_PATHBITBUCKET_API_TOKENBITBUCKET_DEFAULT_PAGE_SIZEATLASSIAN_DC_MCP_CONFIG_FILEATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 105 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Atlassian Dc MCP Bitbucket | View Git Summary |
Tools & capabilities
Atlassian Dc MCP Bitbucket tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
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"
}
}
}
}
Git Summary
{
"mcpServers": {
"git-summary": {
"command": "npx",
"args": [
"-y",
"git-summary-mcp"
]
}
}
}
Frequently asked questions
Atlassian Dc MCP Bitbucket is categorized under Version Control and uses a local stdio subprocess. Git Summary belongs to Version Control and uses a local stdio subprocess. Pick Atlassian Dc MCP Bitbucket for version control work and Git Summary 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.
Atlassian Dc MCP Bitbucket has no declared pricing — check the project's own site. Git Summary 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 atlassian-dc-mcp-bitbucket-2 and git-summary as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Atlassian Dc MCP Bitbucket has a quality signal of 51/100 (Good) with 1 views, 0 installs and 105 GitHub stars. Git Summary has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.