GitHub Repository Intelligence vs Atlassian Dc MCP Bitbucket

A side-by-side look at the GitHub Repository Intelligence 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.

GitHub Repository Intelligence logoGitHub Repository IntelligenceVersion Control · Remote HTTP/SSERepo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.48FairAuth: not declaredAtlassian Dc MCP Bitbucket logoAtlassian Dc MCP BitbucketVersion Control · Local subprocess (stdio)MCP server for Atlassian Bitbucket Data Center - interact with repositories and code51GoodAuth: not declared

Verdict: choose GitHub Repository Intelligence for version control work over a hosted endpoint; 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?

GitHub Repository Intelligence logoChoose GitHub Repository Intelligence when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: APIFY_TOKEN.
  • You want tools like get_repo_overview, list_recent_prs, get_contributors.
Explore GitHub Repository Intelligence

Atlassian Dc MCP Bitbucket logoChoose 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.
Explore Atlassian Dc MCP Bitbucket

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGitHub Repository Intelligence logoGitHub Repository IntelligenceAtlassian Dc MCP Bitbucket logoAtlassian Dc MCP Bitbucket
CategoryVersion ControlVersion Control
Quality signal48/100 · Fair51/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsAPIFY_TOKENBITBUCKET_HOSTBITBUCKET_API_BASE_PATHBITBUCKET_API_TOKENBITBUCKET_DEFAULT_PAGE_SIZEATLASSIAN_DC_MCP_CONFIG_FILEATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS
Verified ownerCommunity listingCommunity listing
GitHub stars0105
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools6Not listed

Tools & capabilities

GitHub Repository Intelligence tools 6

  • get_repo_overview"Is this repo still maintained?"
  • list_recent_prs"Show me the last 20 merged PRs by user X"
  • get_contributors"Who maintains this project?"
  • get_hot_files"Where's the churn?"
  • get_ci_status"Is the default branch green?"
  • get_dependencies"What does this project depend on?"

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.

GitHub Repository Intelligence

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "github-repository-intelligence": {
      "url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp"
    }
  }
}

Atlassian Dc MCP Bitbucket

mcpServers (Claude Desktop / Cursor)
{
  "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

GitHub Repository Intelligence is categorized under Version Control and uses a remote HTTP/SSE transport. Atlassian Dc MCP Bitbucket belongs to Version Control and uses a local stdio subprocess. Pick GitHub Repository Intelligence 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.

GitHub Repository Intelligence 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 github-repository-intelligence 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, GitHub Repository Intelligence has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Atlassian Dc MCP Bitbucket has 51/100 (Good) with 1 views, 0 installs and 105 GitHub stars.