Skip to main content
Glama
Nishant-Chaudhary5338

mcp-code-indexer-react-ts

by Nishant-Chaudhary5338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-code-indexer-react-ts

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

    • Octocode

      Muvon
      A
      license
      Not graded
      quality
      A
      maintenance
      Semantic code indexer with GraphRAG knowledge graph. Index your codebase, search in natural language, and expose everything via MCP so AI agents understand architecture — not just files.
      474
      Apache 2.0

    • Idencify

      jospnunes
      A
      license
      B
      quality
      C
      maintenance
      Whole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic code search — 14 tools via hosted MCP endpoint.
      15
      MIT

    • minh-gkg

      Minh090506
      A
      license
      Not graded
      quality
      B
      maintenance
      Compiler-exact TypeScript code graph MCP server exposing find-references, change impact analysis, and repo map tools for AI agents, powered by the TypeScript compiler via ts-morph.
      MIT

    • code-graph-mcp

      dorkian
      A
      license
      A
      quality
      B
      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
    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.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is minor overlap between 'find_references', 'who_calls', and 'who_renders' since all deal with incoming edges. However, descriptions clearly differentiate them by edge type.

    Naming Consistency4/5

    Naming is mostly verb_noun (e.g., index_repo, search_nodes, find_cycles), but 'blast_radius' breaks the pattern with a noun phrase. The 'who_' prefix for call/renders is consistent but unconventional.

    Tool Count5/5

    14 tools is a well-scoped set for a code indexing server, covering indexing, searching, dependency analysis, and visualization without excessive overlap.

    Completeness4/5

    Covers core CRUD (index, read, search) and dependency analysis thoroughly. Missing explicit delete or update tools for the graph, but the server's read-heavy purpose makes this acceptable.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources