All servers / Security / Codacy MCP server
Codacy MCP server
Codacy MCP server
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.7.5. Package: @codacy/codacy-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (88.4 seconds including download)
- Tools offered: 4
- Last published: 2026-11-18
- Weekly downloads (npm): 3,214
- License: MIT · Direct dependencies: 7
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
codacy_get_pattern2 of 2 parameters describedGet the definition of a specific pattern. Common use cases: - When the user asks for the definition of a specific pattern - When the user asks for more information about an issue found by Codacy Common mistakes: - Using this tool with the wrong toolUuid - Using this tool with the wrong patternId
codacy_list_tools2 of 2 parameters describedList all code analysis tools available in Codacy.
codacy_cli_analyze6 of 6 parameters describedRun quality analysis locally using Codacy CLI. Use this tool to analyze the quality of a repository using Codacy command line. Common use cases: - When the user asks for an analysis of a repository - When the user asks to scan the code - When the user wants to analyze based on Codacy configuration - When the user wants to apply fixes based on Codacy configuration and analysis - When the user wants Codacy results immediately without waiting for the next scheduled analysis Common mistakes: - Using this tool to know the status of a repository - Using this tool without specifying the rootPath - Using this tool to know current results from Codacy. Use codacy_get_repository_with_analysis instead. - Filling the tool parameter when not asked specifically for it. - Using this tool for a organization other than the current one - Using this tool with the wrong organization name (if you are not sure, use the codacy_list_organizations tool to validate the organization name) - Using this tool without specifying the repository name - Using this tool for a repository other than the current one - Using this tool with the wrong repository name (if you are not sure, use the codacy_list_organization_repositories tool to validate the repository name)
codacy_cli_install3 of 3 parameters describedInstall the Codacy CLI used for local analysis. Common use cases: - When the user tried to use Codacy CLI and it is not installed Common mistakes: - Using this tool for a organization other than the current one - Using this tool with the wrong organization name (if you are not sure, use the codacy_list_organizations tool to validate the organization name) - Using this tool without specifying the repository name - Using this tool for a repository other than the current one - Using this tool with the wrong repository name (if you are not sure, use the codacy_list_organization_repositories tool to validate the repository name)
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.