Codacy MCP server

What the model can do

Codacy code quality: organizations, repositories with grade, issue count, complexity, duplication and coverage, issues found in a repository by severity, category and language with an overview of counts, pull requests and commits with new and fixed issues and whether they meet the quality gates, and branches; when you ask, can ignore or unignore issues and files, reanalyze a commit, trigger an AI review of a pull request, bypass a pull request's analysis status, add, follow, unfollow or delete a repository, turn branch analysis on or off, set the default branch, and add or remove people.

Reads

• codacy_list_organizationsOrganizations the token's user belongs to in Codacy, with the provider code and name every other Codacy tool takes ("gh/acme").
• codacy_list_repositoriesRepositories of a Codacy organization with their quality: grade (A to F), issue count and percentage, lines of code…
• codacy_get_repositoryOne repository's Codacy quality, optionally for a branch enabled on Codacy: grade, issues, complexity, duplication…
• codacy_search_issuesIssues Codacy found in a repository, filtered by severity, category, language, pattern or branch: file and line, severity, category, pattern, tool…
• codacy_get_issues_overviewHow many issues a repository has, counted by severity, category, language, pattern and tag, with the same filters as codacy_search_issues.
• codacy_list_pull_requestsPull requests of a repository as Codacy analysed them, most recently updated first: new and fixed issues, complexity and duplication change…
• codacy_list_commitsCommits of a repository's branch with Codacy's results: new and fixed issues, complexity and duplication change, coverage and its change…
• codacy_list_branchesBranches of a repository on Codacy: which is the default and whether Codacy analyses each.

Acts, when you ask

These change something in Codacy. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• codacy_ignore_issueIgnores one Codacy issue in a repository, with an optional reason and comment, so it stops counting toward the repository's issues and quality gates.
• codacy_unignore_issueBrings back an ignored Codacy issue, so it counts toward the repository's issues and quality gates again.
• codacy_bulk_ignore_issuesIgnores the Codacy issues named by id in one repository, at most 100 at a time, with an optional reason and comment.
• codacy_set_file_ignoredIgnores a file in a repository's Codacy analysis (ignored true), so its issues and metrics stop counting, or brings it back (ignored false).
• codacy_reanalyze_commitAsks Codacy to analyse a commit of a repository again (clean_cache clears its cache first).
• codacy_trigger_ai_reviewAsks Codacy's AI reviewer to review a pull request now.
• codacy_bypass_pull_requestBypasses Codacy's analysis status on a pull request, so its quality gate no longer blocks it and a merge rule waiting on the Codacy check can pass…
• codacy_add_repositoryAdds a repository from the Git provider to its organization on Codacy, which starts analysing it.
• codacy_follow_repositoryFollows a repository that is already on Codacy, so it appears in the token user's list and dashboards.
• codacy_unfollow_repositoryUnfollows a repository on Codacy for the token's user.
• codacy_delete_repositoryDeletes a repository from Codacy, permanently: its Codacy analysis results and settings go for everyone in the organization.
• codacy_set_branch_analysisTurns Codacy analysis of a repository branch on (enabled true) or off.
• codacy_set_default_branchMakes a branch the repository's default branch on Codacy, which its grade, issues and dashboards then follow.
• codacy_add_peopleAdds the people named by email to a Codacy organization, as members or committers (Codacy decides by whether they asked to join)…
• codacy_remove_peopleRemoves the people named by email from a Codacy organization, so they lose its access on Codacy.

Connect it

First connect Codacy on Dashboard → Connections, then add Memtro to your client once. The Codacy tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Codacy connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which repositories have the most critical issues?
• › How many security issues does the api repository have?
• › Which open pull requests fail the quality gates?
• › What is the coverage on the main branch of web?
• › Ignore issue 4821 in api as a false positive.

Questions

Is this an official Codacy MCP server?

No. It is Memtro's MCP server with Memtro's Codacy connector behind it: the connector reads Codacy through its API with the credentials you connect on Dashboard → Connections, and Codacy publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Codacy?

Only when you ask, and only what it has been granted: ignore an issue, with a reason; unignore an issue; ignore up to 100 issues by id; ignore or unignore a file in analysis; reanalyze a commit; trigger an AI review of a pull request; bypass a pull request's analysis status (its quality gate no longer blocks); add a repository to Codacy; follow a repository already on Codacy; unfollow a repository; delete a repository from Codacy (permanent, the Git repository is untouched); turn analysis of a branch on or off; set a repository's default branch; add people to an organization by email; remove people from an organization by email. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server