mcpField
R
Rami Code Review

Rami Code Review

Remote
rami.reviewsDeveloper Tools0Updated today

About Rami Code Review

Rami Code Review reviews pull requests for security issues, bugs, and performance risks, then supports an agent-driven fix and dispute loop. It is designed for Claude Code and Codex, with findings handled by priority and human control over merges.

Key features

  1. 01Pull request code reviews
  2. 02Prioritized review findings
  3. 03MCP-based finding retrieval and fixes
  4. 04Evidence-based finding disputes
  5. 05Review status and quota commands

Use cases

  1. 01Review a pull request before merging
  2. 02Have an agent fix flagged issues
  3. 03Dispute an incorrect or duplicate finding

MCP support

MCP tools let Claude Code and Codex retrieve review findings and work through fixes or disputes. The plugin provides setup for registering the MCP server and verifying its connection.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://rami.reviews/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Rami

Rami Code Review

Works with Claude Code AND Codex. Rami reviews every PR for security, bugs, and performance — then fixes the findings through MCP. You stay in control of what merges.

Both clients are first-class: Claude Code loads the root plugin package, while Codex installs its isolated package from plugins/rami through the same marketplace repository.

Rami PR check

Disputing Findings

Not every finding needs a fix. Push back when you have evidence — Rami evaluates the dispute and either accepts it or asks you to fix:

  • False positive — the code is actually correct
  • Framework guarantee — the framework handles this case
  • Intentional design — this is by design, not a mistake
  • Duplicate — the same issue is reported elsewhere

The dispute loop runs in the same session as the review, so accepted disputes drop out and only real issues land in your commits.

Getting Started

1. Install the GitHub App

Install Rami on your repository.

2. Add the marketplace

Claude Code:

/plugin marketplace add rami-code-review/claude-code-marketplace

Codex:

codex plugin marketplace add rami-code-review/claude-code-marketplace
3. Install the plugin

Claude Code:

/plugin install rami@rami-code-review

Codex:

codex plugin add rami@rami-code-review

Start a new Codex task after installation so the Rami skills and MCP tools are loaded.

4. Run a review

On a PR branch, run:

/rami:review

Rami fetches the review, walks each finding by priority, and applies fixes (or accepts disputes) until the PR is clean.

Commands

/rami:review

Full review-fix-dispute loop on the current PR branch:

  • Fetches review results
  • Walks findings by priority (blocking → high → medium → low)
  • Fixes each one — or lets you dispute with evidence
  • Commits and pushes
  • Repeats until clean (up to 5 iterations)
/rami:review-status

Check review status without triggering a new review.

/rami:usage

Check remaining quota and credit balance.

/rami:setup

Guided setup — installs the GitHub App, registers the MCP server, completes OAuth, and verifies the connection. Run this first if Rami isn't connected yet. It can also offer, only if you agree, to add a short removable Rami section to your CLAUDE.md / AGENTS.md.

/rami:doctor

Read-only health check. Reports auth, GitHub App coverage, quota, and whether the plugin is up to date — with the fix for anything that's off.

/rami:upgrade

Updates the plugin to the latest published version and shows what changed.

Troubleshooting

"No PR found for branch" — push the branch and open a pull request.

"Authentication required" — install the Rami GitHub App on the repo.

Review taking too long? — /rami:review-status checks progress without triggering a new review.

Keeping Rami up to date

Rami checks once a day — silently — whether a newer plugin version is published, and nudges you when one is. To update at any time:

/rami:upgrade

Or manually:

claude plugin marketplace update rami-code-review
claude plugin update rami@rami-code-review

Then run /reload-plugins (or start a new session) to activate it.

For Codex:

codex plugin marketplace upgrade rami-code-review
codex plugin add rami@rami-code-review

Then start a new task to activate the updated plugin.

Links

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.