codacy

The Codacy MCP Server provides an interface to access Codacy's APIs for repositories, files, quality metrics, security findings, and various analyses. It exposes a suite of tools such as repository setup, organization and repository management, code quality and analysis, file management and analysis, security analysis, pull request analysis, tool and pattern management, and a CLI analysis feature. With the MCP Server running, you can query Codacy resources for repositories, obtain file-level and repository-level metrics, list issues and patterns, and run local analyses via the Codacy CLI integration when desired. The server acts as a bridge that lets you programmatically manage Codacy data and run analyses through standardized MCP tools.

To use it, configure the MCP server in your environment (for example in Cursor, Windsurf, Claude Desktop, or VS Code integrations) with the provided command and install token. The common entrypoint is the Codacy MCP package, which you install via npx and provide your Codacy account token as an environment variable. Once configured, you can call the available tools (e.g., codacy_list_repository_issues, codacy_get_file_with_analysis, codacy_search_repository_srm_items) to retrieve analysis results, issue lists, and security findings for your repositories.

Prerequisites

• git
• Node.js (ensure npx is available in your environment)
• A Codacy account with a Personal API Access Token

Installation options

1. One-click or IDE integration (recommended):

• Install Codacy MCP Server through your IDE extension or marketplace following the documentation, then use the provided one-click install snippets.

2. Manual installation via npx (Node.js):

• Run the following command to install and run the MCP server placeholder for Codacy:

npx -y @codacy/codacy-mcp

• When prompted, provide your Codacy account token via the CODACY_ACCOUNT_TOKEN environment variable. Example configuration (for editors like Cursor/Windsurf or CLAUDE Desktop):

{
  "mcpServers": {
    "codacy": {
      "command": "npx",
      "args": ["-y", "@codacy/codacy-mcp"],
      "env": {
        "CODACY_ACCOUNT_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

3. Alternative: use the specific npm package name directly in your MCP config

• Package name: @codacy/codacy-mcp
• Ensure you provide CODACY_ACCOUNT_TOKEN in env as shown above.

Prerequisite steps

• Obtain your Codacy Account API Token from your Codacy account page.
• Ensure your environment can access npm crates or the npm registry as needed.
• If using Codacy CLI locally for analysis, ensure Codacy CLI v2 is installed or automatically installed by the MCP Server as described in the repository docs.

Tips and common issues:

• Make sure CODACY_ACCOUNT_TOKEN is kept secret and not exposed in public configs.
• The MCP Server relies on Node.js and npx; ensure your shell environment has network access to fetch the required package from npm.
• If you upgrade the MCP Server package, re-check environment variable names and argument lists, as they may change across versions.
• For IDE integrations (Cursor, Windsurf, VS Code), you can typically paste the JSON snippet into your mcp_config.json or equivalent file to wire up the codacy server entry.
• If you encounter authentication errors, regenerate or re-validate your Codacy API token and ensure it has necessary scopes for the operations you perform (repositories, analyses, and security items).
• When using the Codacy CLI locally, the MCP Server will attempt to install it if not present; ensure your environment allows such installations.