← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionCodacy MCP ServerQuery Codacy's code quality, security, and coverage analysis via MCP.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS56 / 100 · C76 / 100 · B
Reliability8 / 2013 / 20
Security and permissions10 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Teams already using the Codacy platform for code quality and security management
  • Developers who want Codacy analysis results directly inside Cursor, Windsurf, VS Code Copilot, or Claude Desktop
  • Teams that want to check pull request issues and coverage as part of an AI coding assistant workflow
  • 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 without a Codacy account, or who don't intend to register repositories with Codacy
  • Scenarios requiring generic static analysis or security scanning independent of the Codacy platform
  • Restricted environments where Node.js/npx or the Codacy CLI cannot be installed
  • 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
  • Accesses organizations and repositories the user has permission to on Codacy, via the CODACY_ACCOUNT_TOKEN personal account token
  • Reads repository analysis results, issues, coverage, security findings, and pull request data
  • Executes the Codacy CLI locally to analyze code on the filesystem (attempts automatic installation of the CLI)
  • 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
  • CODACY_ACCOUNT_TOKEN is a sensitive credential; if leaked it could grant access to all Codacy organizations and repositories tied to the account
  • codacy_cli_analyze installs and runs the Codacy CLI locally, which involves executing a third-party binary
  • Security-related tools (SRM items) surface repository vulnerability and secret-scanning results, so access and downstream handling should be controlled
  • The server depends on network access to the Codacy API; misconfigured credentials could expose data to unintended clients
  • 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 clientsClaude Desktop, Cursor, Windsurf, GitHub CopilotClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools2315