Skip to main content
Glama

Related Servers

Alternatives to Review MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      F
      maintenance
      Connects AI assistants like Claude to the Codex CLI for code analysis, editing, and execution. Supports file references with @ syntax, sandboxed code execution with approval workflows, and structured code changes for automated refactoring and documentation.
      8
      93 npm
      177
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code to submit code, diffs, plans, and security or edge-case questions to Codex, Gemini, and GPT-OSS for read-only review, verifying each quoted line against the real files so fabricated findings are filtered before Claude reads them. It also runs multi-family councils that surface agreement, falls back across models when quotas run out, and supports optional hooks that block git push until edits have been reviewed.
      10
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Bridges Claude and OpenAI's Codex CLI for AI-powered code analysis, generation, and review, with support for session management, web search, and structured output.
      6
      820 npm
      643
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interactive GitHub pull-request review from Claude Code, with tools to fetch PRs, inspect files and repo structure, post review comments, and query a RAG index of the codebase.
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct with clear boundaries: check_cli_status verifies CLI availability, while review_code, review_directory, and review_file handle code reviews at different granularities. However, review_directory and review_file could be slightly confused as both target files, but their descriptions clarify the scope difference (directory vs. single file).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: check_cli_status, review_code, review_directory, and review_file. This predictability makes it easy for an agent to understand and select tools without confusion.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of code review CLI integration. Each tool earns its place by covering distinct aspects: checking availability and reviewing code at different levels (string, file, directory). This count is neither too thin nor excessive.

    Completeness4/5

    The tool surface covers the core workflows for code review using CLIs: checking availability and performing reviews. A minor gap exists in not providing tools to manage or configure the CLIs (e.g., setting API keys), but agents can work around this as the essential review operations are fully supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues