Skip to main content

importlens-mcp

PyPI version License: MIT

Stop feeding your coding agent the whole repo. Feed it the files that actually matter.

importlens-mcp is a tiny MCP server that reads your Python project's import graph and hands your agent only the slice of code relevant to what it's working on — the file that defines a symbol, the files that use it, and the files it depends on. No embeddings, no vector DB, no re-reading the tree on every question.

npx-style one-liner for python:  uvx importlens-mcp

Why: on a big repo, agents burn tokens (and get confused) re-reading files that have nothing to do with the task. importlens-mcp answers "which files matter for UserService?" in one call, using nothing but Python's own ast.

demo


Install

# with uv (recommended)
uvx importlens-mcp            # run straight from PyPI, no install

# or pip
pip install importlens-mcp

Add it to your agent. For(what I use) Claude Code:

claude mcp add importlens-mcp -- uvx importlens-mcp

For any MCP client, point it at the importlens-mcp command (stdio transport). It indexes the current working directory by default, or set IMPORTLENS_ROOT.

What your agent gets

Four tools, all returning plain readable text:

tool what it does
project_map one-glance summary: files, modules, symbols, line count
relevant_files(symbol) the files that define a symbol + its dependents + its dependencies
file_context(path) one file's source plus the paths of its local imports
reindex rebuild after you change files on disk

Example

Ask your agent "how does CodeIndex fit together?" and under the hood it calls:

relevant_files("CodeIndex")
# Relevant files for `CodeIndex`

## Defined in
- src/importlens_mcp/graph.py

## Used by (dependents)

### src/importlens_mcp/__main__.py
```python
   1  from importlens_mcp.graph import CodeIndex, call_sites
...
  22      idx = CodeIndex(str(root)).build()
  23      s   = idx.stats()
  24      ...

src/importlens_mcp/server.py

   1  from .graph import CodeIndex, call_sites
...
  34      _index = CodeIndex(_ROOT).build()

Depends on (local imports)

  • (none)

Dependents show only the lines that use the symbol (+ a few lines of context), not the whole file. Pass `include_full_dependents=True` to get file paths instead.

## Quick look without an agent

```bash
importlens-mcp map .
importlens-mcp: 4 files, 4 modules, 10 symbols, 371 lines
  importlens_mcp           src/importlens_mcp/__init__.py
  importlens_mcp.graph     src/importlens_mcp/graph.py
  importlens_mcp.server    src/importlens_mcp/server.py
  ...

How it works

  1. Walk the repo, skipping the usual noise (.venv, node_modules, __pycache__, …).
  2. Parse each .py file with the standard-library ast module — top-level functions/classes become symbols, import statements become edges.
  3. Build two maps: symbol -> files that define it and module -> files that import it.
  4. Answer queries by walking those maps. No network, no model calls, runs in milliseconds.

Import resolution is best-effort and handles src/ layouts and relative imports. It won't catch dynamic imports or runtime magic — and that's a fine tradeoff for a v0.

Benchmark

Four strategies compared on two real repos. Token estimate: len(source) // 4.

  • all files — every source .py file (worst-case baseline)
  • grep full files — files whose text contains the symbol name, plus their direct local imports, all read in full (naive agent behaviour)
  • grep -C3 — fairer smart-grep: defining file read in full, every other mentioning file as a 3-line-context snippet (what a careful agent would actually do)
  • importlens — what relevant_files() returns: defining file + local imports in full, dependent files as call-site snippets (2 lines before + 3 after each match)
repo symbol all files grep full files grep -C3 importlens % saved vs grep -C3
trading-bot RiskManager 8,187 7,884 912 842 +8%
trading-bot TradingBot 8,187 7,884 1,821 3,630 −99%
trading-bot BacktestEngine 8,187 7,884 1,557 2,886 −85%
httpx DigestAuth 71,089 53,965 3,017 18,377 −509%
httpx Timeout 71,089 61,102 3,045 19,799 −550%
httpx MultipartStream 71,089 9,436 2,603 5,403 −108%
httpx Client 71,089 65,077 17,514 51,865 −196%
httpx Request 71,089 66,452 16,113 33,897 −110%

Honest take: importlens beats grep -C3 only when the symbol is well-isolated — RiskManager wins by 8% because grep matches many files that happen to mention the name, while importlens knows exactly which file defines it. For everything else importlens is more expensive, because it insists on reading the full defining file and all its local imports, not just snippets.

That cost is intentional. Grep -C3 gives you fragments: enough to see call sites, not enough to safely modify the implementation. Importlens gives you the full understanding cone — the implementation plus everything it depends on — so your agent can reason about the code rather than just locate it. If you only need to know where Timeout is called, grep -C3 is cheaper. If you need to change how it works, the extra tokens pay for themselves.

Rerun with python benchmarks/bench.py (httpx needs git clone --depth=1 https://github.com/encode/httpx /tmp/httpx first).

Roadmap

  • call-graph edges (who calls this function), not just imports
  • respect .gitignore
  • method-level symbols, not just top-level
  • tree-sitter backend for speed on huge repos

Contributing

It's ~370 lines of plain Python. Read it, break it, send a PR. Good first issues are labeled.

License

MIT

Metadata

Release files for importlens-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for importlens-mcp 0.2.0
File Size Uploaded Provenance Actions
importlens_mcp-0.2.0.tar.gz 137.5 kB Without provenance Details for importlens_mcp-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for importlens-mcp 0.2.0
File Interpreter ABI Platform Actions
importlens_mcp-0.2.0-py3-none-any.whl Python 3 none any Details for importlens_mcp-0.2.0-py3-none-any.whl

Total release size: 148.6 kB

Release files / importlens_mcp-0.2.0.tar.gz

Download URL importlens_mcp-0.2.0.tar.gz
Size 137.5 kB
Tags Source
SHA-256 checksum
How to use checksums
4b06fb083633df7c680cc5981b89c60c43b569ccd96e570faf2685be0a56ecd1
BLAKE2b-256 checksum
How to use checksums
fbb61283906325dff7cb5230abc5219145a203011d82c6efb4d082ac4d6a77f5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Release files / importlens_mcp-0.2.0-py3-none-any.whl

Download URL importlens_mcp-0.2.0-py3-none-any.whl
Size 11.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1a3c8671e2c250df92664a3ef1f33abf303cc294780069936a469727c1c9faf6
BLAKE2b-256 checksum
How to use checksums
a24c17e30280e3aac87ab148800369a0a7aee6f60123df1449484dc27eda1cb9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Security for importlens-mcp 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page