importlens-mcp
Related Servers
Alternatives to importlens-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to navigate and query source code by providing context, symbols, and call graph information through a graph index.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a local structural code graph, inspect relationships and impact, and retrieve focused project context before reading full files.24 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityBmaintenanceEnables symbol-level codebase retrieval, providing definitions and usages of symbols to agents without reading whole files.ISC
- FlicenseAqualityDmaintenanceEnables blast-radius enforcement for coding agents by building an AST call/dependency graph and injecting a symbol's callers into the agent's context at the moment it edits a file.13-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve precise symbol definitions and usages from codebases, eliminating the need to fetch entire files.10 npm2ISC
TDQS
Scored across 4 tools
The three read tools have separable entry points: project_map is a whole-repo summary, relevant_files is keyed by a symbol name, and file_context is keyed by a file path. relevant_files and file_context could be momentarily confused (both 'return the slice I need'), but the descriptions explicitly distinguish symbol-centric vs path-centric usage.
All names are lowercase snake_case and readable. Three are noun compounds (project_map, relevant_files, file_context) while reindex is a bare verb, so there's no uniform verb_noun pattern, but the style is internally coherent enough to predict new names.
Four tools is on the lean side but each covers a distinct entry point in a code-navigation workflow, and no tool is redundant. A read-only indexer arguably needs only this set, though one more capability (search) would round it out.
Overview, symbol drill-down, file read, and reindex cover the main lifecycle of index-then-explore, but there is no text/pattern search or symbol listing, so an agent cannot locate code when it doesn't already know the symbol or file name. That is a notable gap, workable around only via repeated file_context reads.