Cursor Reviewer MCP
Related Servers
Alternatives to Cursor Reviewer MCP
No user-submitted related servers found.
Related Servers
- -licenseCqualityNot gradedmaintenanceEnables comprehensive GitHub PR reviews through Cursor's AI by fetching PR diffs, running static analysis tools (ESLint, Prettier, TypeScript, Semgrep), executing tests, and generating detailed code review reports with inline comments.91,632 npm1-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered code review and improvement, including analysis, refactoring suggestions, and automatic test generation, with an optional agentic loop for iterative refinement.MIT
- FlicenseAqualityDmaintenanceEnables Claude to perform thorough code reviews by integrating with Codex and Gemini CLIs to provide senior-level feedback on code quality, security, performance, and best practices. Supports reviewing code snippets, individual files, or entire directories with automatic detection of available review tools.4-
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate tasks to Cursor's headless agent, run adversarial reviews, and verify findings with prosecutor/advocate roles.79 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to perform code reviews by providing access to staged files, git diffs, and repository file content. It allows users to evaluate changes and context within any local git repository before committing or pushing.34 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run security and code review on pull requests and diffs, exposing review_pr and review_diff capabilities with local-first analyzers and LLM explanations.2MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: codex.review uses Codex CLI, while cursor.review uses Cursor CLI with GPT-5. There is no overlap in functionality as each targets a different review system, making misselection unlikely.
Both tools follow a consistent naming pattern: they use a prefix (codex or cursor) followed by a dot and the action 'review'. This pattern is uniform across all tools, making them predictable and easy to identify.
With only 2 tools, the server feels thin for a 'Cursor Reviewer' domain, as it lacks operations like listing reviews, updating reviews, or handling review feedback. The count is too low to support comprehensive review workflows.
The tool surface is severely incomplete for a review system; it only provides review creation via two CLI methods, missing essential CRUD operations such as retrieving, updating, deleting reviews, or managing review-related data. This will likely cause agent failures in broader tasks.