← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBitbucket MCP ServerA Model Context Protocol (MCP) server for Bitbucket Cloud and Server API integration.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS52 / 100 · D76 / 100 · B
Reliability4 / 2013 / 20
Security and permissions10 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Developers using Bitbucket Cloud or Server who want AI assistant integration.
  • Teams that need to interact with Bitbucket repos and PRs programmatically or via natural language.
  • Users leveraging MCP standard to operate Bitbucket within tools like Cursor.
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users who need delete operations on Bitbucket resources (delete tools are disabled by default).
  • Users who need a GUI instead of CLI or AI integration.
  • Users without Bitbucket credentials.
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Requires Bitbucket app password or access token.
  • Needs at least 'Repositories: Read' for most operations.
  • For pipeline operations, 'Pipelines: Read' is required.
  • For write operations (e.g., create/update PRs), 'Pull requests: Write' is required.
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • Using app passwords or tokens may lead to unauthorized access if leaked.
  • Overly permissive credentials might allow unintended modifications or deletions (though delete tools are disabled by default).
  • Misconfiguration could expose sensitive information (e.g., incorrect logging levels).
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsCursor, Claude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools4015