Skip to main content
Glama
SurajKGoyal

myopic

by SurajKGoyal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to myopic

No user-submitted related servers found.

    Related Servers

    • code-reviewer-mcp

      ArthDh
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that performs automated code reviews by analyzing git diffs against configurable review standards with custom reviewer personas.
      7
      2
      MIT

    • leveret

      leveret-dev
      A
      license
      A
      quality
      A
      maintenance
      Self-hosted MCP engine for private code reviews, providing deterministic static analysis and AST-level search over diffs, with findings passed to a review agent of your choice.
      5
      2
      AGPL 3.0

    • mcp-review-pr

      thangtn83
      F
      license
      A
      quality
      D
      maintenance
      An MCP server for multi-language PR review with deterministic analysis, providing AI-powered code review tools that detect languages, apply review guidelines, and run quality checks.
      7
      -
    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

    A4.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: MR summary, raw diff vs. sectioned diff, review status, thread verification, comment posting, and separate local analysis tools (dependency_impact, trace_call_chain, code_search). Even the two diff tools are explicitly differentiated by structured sections vs. raw hunks, with guidance on when to prefer each.

    Naming Consistency4/5

    Tool names are mostly predictable: MR-related tools share the `mr_` prefix, and indexing tools share `index_`. However, the underlying verb/noun pattern is not fully uniform (e.g., `code_search` vs. `index_repo`, `mr_diff_sections` vs. `mr_verify_review`), though all names are descriptive and support quick recognition.

    Tool Count5/5

    12 tools is well-scoped for a code review assistant. Each tool covers a distinct step: changed-file summary, diff variants, review status, verification, posting, and local repository analysis (dependency, call graph, semantic search). No tool feels redundant or missing.

    Completeness5/5

    The tool set covers the full MR review lifecycle—orient (mr_changed_files, mr_review_status), inspect (mr_diff_lines, mr_diff_sections), analyze impact (dependency_impact, trace_call_chain, mr_review_context), verify threads (mr_verify_review), and act (mr_post_comments). Local indexing and search tools round out the surface, leaving no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources