Codacy + Memtro

Which repositories have the most critical issues, and which pull requests fail the gates?

Codacy grades your code. Memtro reads repositories with grade, issues, complexity, duplication and coverage, issues by severity, category and language, and pull requests and commits with new and fixed issues against the quality gates. When asked and granted, it can ignore or unignore issues and files, reanalyze a commit, trigger an AI review, bypass a pull request's status, add, follow or delete a repository, change branch settings and add or remove people. Codacy can tell Memtro when an analysis finishes, and a job can start on it. Codacy webhooks need its Business plan and an organization admin or manager.

In Memtro

What you can do with Codacy in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Codacy tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Rank repositories by grade, issue count, complexity, duplication and coverage, with any setup problem.
  2. 02Find issues by severity, category, language or pattern, with file, line and false-positive likelihood, or count them.
  3. 03Check pull requests and commits for new and fixed issues, coverage change and which quality gates fail.
  4. 04When asked and granted, ignore or unignore issues and files, reanalyze a commit, or trigger an AI review, which can comment on the pull request where its participants see it.
  5. 05When asked and granted, bypass a pull request's Codacy status, add, follow or delete a repository, change branch settings, or add or remove people.
  6. 06With events on, Codacy finishing an analysis of a branch or pull request can start a job.

Acts when asked

When you ask it to

These tools change something in Codacy. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Ignore an issue, with a reason
  2. 02Unignore an issue
  3. 03Ignore up to 100 issues by id
  4. 04Ignore or unignore a file in analysis
  5. 05Reanalyze a commit
  6. 06Trigger an AI review of a pull request
  7. 07Bypass a pull request's analysis status (its quality gate no longer blocks)
  8. 08Add a repository to Codacy
  9. 09Follow a repository already on Codacy
  10. 10Unfollow a repository
  11. 11Delete a repository from Codacy (permanent, the Git repository is untouched)
  12. 12Turn analysis of a branch on or off
  13. 13Set a repository's default branch
  14. 14Add people to an organization by email
  15. 15Remove people from an organization by email

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Codacy for you. Each event can start a job, with the event as its input. Codacy signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01Codacy finished analysing a branch or pull request (success, partial or failure)
In practice

Ask it like you would a colleague

Once Codacy is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Codacy + Memtro
  • 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.

01

Worst repositories first

Maya Okafor, an engineering manager at BigCo, asked which repositories had the worst Codacy grade. Memtro listed them with grade, issue percentage, duplication and coverage, so she could pick where the team should start.

02

Gates checked after analysis

Acme Ltd turned on Codacy events so Dan Fletcher, its tech lead, sees failing pull requests early. When Codacy finished analysing a pull request, a job read it and told Dan which quality gates failed and the new issues it added.

Teams

Where it fits

The teams that lean on Codacy most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Codacy is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAccount API token
  1. 1

    In Codacy, open Your account → Access management and create an API token with an expiry of up to one year. Codacy recommends a dedicated service account.

  2. 2

    In Memtro, open Connections → Codacy and paste the Account API token. Add the Default organization, such as gh/acme, if the token belongs to more than one.

  3. 3

    The token has its owner's roles in every organization. An administrator grants the ignore, bypass, repository and people actions by name to the teams that may use them. Events are turned on from the connection's Events tab.

  4. 4

    Ask which repositories have the most critical issues.

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Codacy tools are the same everywhere.

FAQ

Questions

Can Memtro 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. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Codacy connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Codacy data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Codacy?+

Account API token. In Codacy, open Your account → Access management and create an API token with an expiry of up to one year. Codacy recommends a dedicated service account.

Can Codacy start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Codacy for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Codacy in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time