Skip to main content
Glama
importlens-mcp

importlens-mcp

by Matheos13

Related Servers

Alternatives to importlens-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to navigate and query source code by providing context, symbols, and call graph information through a graph index.
      4
      MIT
    • 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables symbol-level codebase retrieval, providing definitions and usages of symbols to agents without reading whole files.
      ISC
    • F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve precise symbol definitions and usages from codebases, eliminating the need to fetch entire files.
      10 npm
      2
      ISC

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues