A
licenseA
qualityD
maintenanceProvides MCP tools to review git changes using OpenAI Codex CLI, enabling code review of unstaged, staged, or last-commit changes.
3
9 npm
MIT
codex-code-review
by Szpadel
Related Servers
Alternatives to codex-code-review
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Grok Build to orchestrate the local Codex CLI for code reviews, adversarial reviews, task rescue, session transfer, and background job management through MCP tools.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate bounded, read-only analysis and isolated patch proposals to the locally installed Codex CLI over MCP, with sanitized live status, revision-aware polling, and reviewable results.1MIT
- AlicenseNot gradedqualityCmaintenanceA local, read-only Git change review tool that provides total workspace diffs, staged/unstaged views, file-level inspection, and task-scoped snapshots for MCP-compatible clients like Codex, Claude Code, and Cursor.MIT
- AlicenseAqualityBmaintenanceEnables an MCP-capable assistant to review GitLab merge requests, GitHub pull requests, and pre-push local branches against ticket requirements, domain rubrics, compiler/lint pre-passes, blast-radius analysis, and SonarQube findings, and to draft inline comments or follow-up tasks in the user's chosen language. Nothing reaches a remote host until a human approves the exact content in an interactive terminal.3MIT
- FlicenseCqualityBmaintenanceEnables Codex to delegate already-scoped coding tasks to Claude Code and manage the resulting execution and fresh read-only review sessions, returning deterministic PASS/FAIL results through a local MCP interface.710-
TDQS
B3.2/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no ambiguity. The agent will always select the same tool for the server's purpose.
Naming Consistency4/5
The single tool name follows a clear verb_noun pattern (review_uncommitted_changes), but consistency cannot be fully assessed with only one tool.
Tool Count2/5
A single tool is very thin for a server. While it may serve a narrow purpose, it feels incomplete and limits the server's usefulness.
Completeness2/5
The tool only covers reviewing uncommitted changes. Obvious gaps include reviewing committed changes, specific files, or providing review history.
Maintenance
ActivityInactive
ResponsivenessUnresponsive