importlens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMPORTLENS_ROOT | No | The root directory to index. Defaults to the current working directory. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_mapA | Summarize the Python project: file count, modules, symbols, lines. Call this first to understand the shape of the repo before drilling in. |
| relevant_filesA | Find the files that matter for a given symbol (function or class name). Returns the file(s) that define it, the call sites in dependent files, and
signatures of the local modules they depend on. This is the slice of the repo
an agent needs to reason about Args: symbol: a top-level function or class name, e.g. "CodeIndex". include_source: if true, also inline the defining files' source. include_full_dependents: if true, list dependent file paths instead of inlining the call sites where the symbol is used. include_full_imports: if true, list local import paths instead of inlining their signatures. |
| file_contextA | Return a file's source plus the paths of its local dependencies. Use this to read one file with awareness of what it pulls in, without loading the whole project. Args: path: repo-relative path, e.g. "src/importlens_mcp/server.py". |
| reindexA | Rebuild the index. Call after you've changed files on disk. |
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 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.