Atlassian Dc MCP Bitbucket vs GitLab API MCP
A side-by-side look at the Atlassian Dc MCP Bitbucket and GitLab API MCP 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 GitLab API MCP for version control over a hosted endpoint. 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 GitLab API MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 51/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Free |
| 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 | 10 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Atlassian Dc MCP Bitbucket | View GitLab API MCP |
Tools & capabilities
Atlassian Dc MCP Bitbucket tools
No tool names declared yet. Check the project README from the listing page.
GitLab API MCP 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.
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"
}
}
}
}
GitLab API MCP
{
"mcpServers": {
"gitlab-api": {
"url": "http://localhost:8000/gitlab-mcp/mcp"
}
}
}