Skip to main content
Glama
RaviIITk

code-index

by RaviIITk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to code-index

No user-submitted related servers found.

    Related Servers

    • codegraph

      mooyee0929
      A
      license
      B
      quality
      C
      maintenance
      Indexes a Python/JS/TS repository into a local SQLite knowledge graph so agents can trace callers, callees, imports, subclasses and covering tests, measure impact radius, rank diff risk, and summarize architecture without grepping files. Exposes these queries as MCP tools alongside an equivalent CLI, with no daemon, embeddings, or network access.
      10
      MIT

    • RepoGraph

      meethjaswani
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to query a local-first code intelligence graph of Python repositories—covering functions, classes, modules, and their relationships—via MCP, supporting subgraph retrieval, caller lookup, and impact analysis without re-reading the codebase.
      -

    • code-graph-mcp

      dorkian
      A
      license
      A
      quality
      C
      maintenance
      Indexes a mono-repo into a knowledge graph and provides MCP tools to query code structure—packages, components, routes, HTTP calls—without file reads or grep round-trips.
      7
      22 npm
      MIT

    • CodeGB

      Killian-Filippov
      F
      license
      Not graded
      quality
      F
      maintenance
      Provides a local code knowledge graph for Java projects, enabling querying of classes, methods, fields, calls, inheritance, and imports via MCP tools like query, context, impact, and cypher.
      1
      -
    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/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: callers, class hierarchy, structural context, dependencies, detailed node info, and SPARQL queries. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Most tools follow the 'get_' prefix pattern (get_callers, get_class_hierarchy, etc.), but query_sparql deviates slightly by using 'query' instead. The naming is still clear and predictable overall.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a code indexing server. Each tool provides essential functionality without redundancy or excess.

    Completeness4/5

    The tools cover structural analysis (context, details) and relational queries (callers, hierarchy, dependencies). The SPARQL endpoint allows arbitrary queries, filling most gaps. Minor missing direct tool for listing all modules, but query_sparql can handle that.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources