mcp-code-indexer-react-ts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INDEXER_ROOT | No | Root path of the repository to index. If not provided, the tool accepts root as an argument. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_repoA | Index a TS/React repo (monorepo or standalone) into a code graph and persist it to .code-graph/graph.json |
| get_graphA | Read the code graph. Defaults to a compact summary on large repos (pass full:true for everything). Narrow with type/depth/lean/fields to keep output small. |
| get_nodeB | Read a single node from the persisted code graph by id |
| who_rendersC | Reverse lookup: which components render the given component id (incoming renders edges) |
| who_callsA | Reverse lookup: which symbols call the given function/component id (incoming calls edges) |
| find_referencesB | All references into a node (incoming edges), optionally filtered by edge type |
| blast_radiusA | Everything that transitively depends on a node — the impact if it changes or breaks |
| find_cyclesB | Find dependency cycles in the graph (import/render/call cycles) |
| find_orphansA | Dead-code candidates: exported files/components/functions that nothing imports, renders, or calls. Excludes entry points (index/main/App/config) unless includeEntryPoints is set. Heuristic — review, do not auto-delete. |
| search_nodesA | Fuzzy-find nodes by name or path (e.g. "useAuth", "Header") — resolve a rough name to canonical node ids without grepping or guessing ids |
| get_context_packA | One dense bundle for safely editing a node: its source + what it depends on + what depends on it + blast-radius size. Use instead of get_node + source + who_calls + blast_radius. |
| build_embeddingsA | Compute local vector embeddings for the indexed nodes (enables semantic_search). Idempotent + incremental — only changed nodes are re-embedded. No-op if the local model is unavailable. |
| semantic_searchA | Find code by MEANING, not just name (e.g. "logic that decides trustee access"). Ranks nodes by embedding similarity; falls back to lexical search (with a hint) if embeddings aren't built. |
| open_explorerA | Start the local 3D web explorer + chatbot for a repo and return its URL. Use when the user asks to SEE/visualize the code graph, open the UI, or explore visually. Starts a background HTTP server on 127.0.0.1 (default port 3002) and indexes the repo; returns the URL to open in a browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
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 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.
14 tools is a well-scoped set for a code indexing server, covering indexing, searching, dependency analysis, and visualization without excessive overlap.
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.