Skip to main content
Glama
isac322

pi-codegraph

by isac322
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pi-codegraph

No user-submitted related servers found.

    Related Servers

    • code-index-pg

      tgt-technology
      A
      license
      A
      quality
      B
      maintenance
      Enables unified code search and analysis over a monorepo, combining exact, semantic, and call graph queries with indexing, incremental updates, and impact analysis.
      12
      MIT
    • koragraph by Koragraph

      koragraphofficial

      Koragraph
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a local, multi-repo code graph for symbol exploration, blast radius analysis, co-change mining, and durable code-anchored memory via MCP tools.
      106 npm
      14
      Business Source 1.1

    • Paseo Semantic Index

      cleverunicornz
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides worktree-aware semantic code indexing and search via MCP, enabling agents to query indexed code and monitor indexing status while keeping lifecycle operations separate.
      MIT

    • Cordyceps Search

      ghassenTn
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.
      -
    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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes: search returns locations, callers/callees handle direct relationships, impact handles transitive reach, and files/status serve different concerns. The main overlap is between codegraph_node and codegraph_explore, both of which can return source and relationships, but the descriptions clarify that node is for a single named symbol or file while explore is for broader code questions.

    Naming Consistency4/5

    All tools share a consistent codegraph_ prefix and use readable lowercase names. The pattern is slightly mixed between noun-style names (node, files, status, callers, callees, impact) and verb-style names (search, explore), but the naming is still predictable and easy to navigate.

    Tool Count5/5

    Eight tools is well-scoped for a code graph query server. Each tool covers a meaningful query mode without redundant bloat, and the count feels appropriate for both simple lookups and deeper dependency analysis.

    Completeness5/5

    The surface covers the core code graph workflow: locating symbols, reading source, viewing file trees, finding callers/callees, assessing transitive impact, exploring related code, and checking index health. No major lifecycle gaps are apparent for a read-only code indexing tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources