Is this an official Codecov MCP server?

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

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 Codecov?

Not yet. Today every Codecov tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

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.

MCP server · Engineering and operations

Codecov MCP server

Codecov in any MCP client, through Memtro: Codecov does not publish this server. Memtro's Codecov connector reads Codecov through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only Codecov: test coverage of the owner's repositories, coverage per commit and per pull request, a pull request's coverage change by file, and the lowest-covered files of a branch.

Reads

codecov_list_reposRepositories of the connected owner in Codecov with their current coverage (percent), language, default branch and when coverage was last updated.
codecov_get_repo_coverageCoverage of one repository at the head of a branch (default: the default branch) or at a commit: overall totals and the files with the lowest…
codecov_list_commitsRecent commits of one repository that Codecov has seen, with coverage, lines missed, whether CI passed and the author.
codecov_list_pullsPull requests of one repository with coverage before and after (base and head), the change, patch coverage and whether CI passed…
codecov_get_pull_comparisonWhat a pull request does to coverage: base, head and patch totals, and the changed files with their coverage before and after.

Connect it

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

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

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

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

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

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

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

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

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 Codecov 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

› Did pull request 42 lower coverage, and where?
› Which repositories have the lowest coverage?
› Which files on main have the lowest coverage?
› What was coverage on the last commit to the release branch?
› Which open pull requests dropped coverage this week?

Questions

Is this an official Codecov MCP server?: No. It is Memtro's MCP server with Memtro's Codecov connector behind it: the connector reads Codecov through its API with the credentials you connect on Dashboard → Connections, and Codecov 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 Codecov?: Not yet. Today every Codecov tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
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.