An MCP server for code review findings in Claude Code, Cursor and Codex

Solemly's MCP server, at https://api.solemly.com/mcp, gives a connected coding agent four tools: list_pr_findings, get_finding, request_review and get_review_status. With it, Claude Code, Cursor or Codex can read the findings on a pull request, fix them, push, request a review and wait for the result.

Checked against the product on 2026-11-03.

The four tools

Tool	What it does
`list_pr_findings`	Lists the findings from the latest review of a pull request, by repository and pull request number or branch, down to a minimum severity.
`get_finding`	Returns one finding in full, by its ID: the file, line, severity, explanation and suggested fix.
`request_review`	Asks Solemly to review a pull request now, like commenting `@solemly review`. `full: true` reviews again even if the latest commit was already reviewed.
`get_review_status`	Reports whether a review is queued, running or done. It can wait up to 50 seconds for a review to finish.

Your agent picks the tools itself. Ask it in plain words: Fix the Solemly findings on this pull request.

Create a token

In Solemly, open the account menu and choose Connect your agent. Create a personal token and copy it: it's shown only once. Tokens start with slm_, expire after 30 days, 90 days, a year or never, and can read findings and request reviews only for the repositories you can see in Solemly.

Connect Claude Code

The Solemly plugin is the quickest way. In Claude Code, run:

/plugin marketplace add Solemly-AI/claude-plugins
/plugin install solemly@solemly

Paste your token when Claude Code asks for it. The plugin adds /solemly:fix, which fixes the Solemly findings on the current pull request, and /solemly:review-loop, which fixes, asks before pushing, waits for the new review and repeats until nothing HIGH or CRITICAL is left. To connect the MCP server without the plugin's commands:

claude mcp add --transport http solemly https://api.solemly.com/mcp \
  --header "Authorization: Bearer slm_your_token"

Connect Cursor

Add this to ~/.cursor/mcp.json, your user settings, so the token stays out of repositories. Then turn on solemly under Settings → MCP.

{
  "mcpServers": {
    "solemly": {
      "url": "https://api.solemly.com/mcp",
      "headers": { "Authorization": "Bearer slm_your_token" }
    }
  }
}

Connect Codex

Codex reads the token from an environment variable, so it never lands in a file:

codex mcp add solemly --url https://api.solemly.com/mcp \
  --bearer-token-env-var SOLEMLY_API_TOKEN

Then set SOLEMLY_API_TOKEN in your shell profile before starting Codex.

Limits and access

Each token can make 240 calls a minute.
A token only sees repositories its user can see in Solemly.
Tokens are created and revoked on the Connect your agent page. If one leaks, revoke it there and create a new one.

Questions

Which coding agents can connect?

Claude Code, Cursor and Codex. Claude Code can also install the Solemly plugin, which adds the /solemly:fix and /solemly:review-loop commands on top of the MCP server.

Can an agent ask for a review?

Yes. request_review asks Solemly to review a pull request now, like commenting @solemly review, and get_review_status can wait up to 50 seconds for the result.

What can a token see?

Only the repositories its user can see in Solemly. Tokens start with slm_, expire after 30 days, 90 days, a year or never, and are created and revoked on the Connect your agent page.

Is there a rate limit?

Yes. Each token can make 240 calls a minute.

In the docs

Try it on your next pull request

Free for 14 days with every feature, no credit card. Install it on a repository and the next pull request gets reviewed.

See pricing