Skip to main content
Glama
shadabbi

Code Review MCP

by shadabbi
OverviewSchemaRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Code Review MCP

No user-submitted related servers found.

    Related Servers

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as static analysis, security scanning, and test running, but there is some potential overlap between 'analysis.run_static' and 'security.run_semgrep' as both involve code analysis, which could cause confusion. The descriptions help clarify their focuses, but the boundaries are not perfectly clear.

    Naming Consistency2/5

    The naming conventions are inconsistent, mixing dot notation (e.g., 'analysis.run_static'), hyphenated names (e.g., 'code-review'), and snake_case (e.g., 'github.fetch_files'). There is no uniform pattern, making the set less predictable and harder for agents to parse reliably.

    Tool Count5/5

    With 9 tools, the count is well-scoped for a code review server, covering key areas like analysis, security, testing, reporting, and integration with GitHub and Jira. Each tool appears to serve a specific function without redundancy, fitting the domain appropriately.

    Completeness4/5

    The toolset covers core code review workflows, including fetching PR data, running analyses, generating reports, and integrating with external systems. A minor gap is the lack of tools for managing or updating review comments or statuses, but agents can work around this with the existing tools.

    Resources