Lenspr
Give your agent a code graph view of the repo so refactors and feature edits do not silently break distant modules.
Overview
Lenspr is a MCP server for the Build phase that exposes a local code graph over stdio so agents can navigate cross-file relationships before applying multi-file edits.
What is this MCP server?
- Builds a code graph so agents see relationships beyond the current open file
- Targets “vibecoding” failures where AI edits compile locally but break other packages
- PyPI package lenspr with stdio MCP transport (v0.1.1)
- Runs locally against your repository—no remote compliance or SaaS dependency
- Open-source repo at github.com/kyrylopr/lenspr
- PyPI package identifier: lenspr
- Published version 0.1.1 with stdio MCP transport
- Source repository: github.com/kyrylopr/lenspr
What problem does it solve?
Agents happily edit one file while unknowingly breaking imports, shared types, and call chains elsewhere in your codebase.
Who is it for?
Indie builders with multi-module repos who rely heavily on agent-driven refactors and need structural context beyond grep.
Skip if: Tiny single-file scripts, teams that forbid local Python tooling, or groups that already run a mature LSP-only workflow with no agent edits.
What do I get? / Deliverables
After you install lenspr and register the MCP server, agents can query graph structure to plan safer refactors across the repository.
- Graph-backed context agents can query before editing related files
- Fewer surprise breakages from cross-module renames and API changes
- Repeatable local MCP setup versioned with lenspr 0.1.1
Recommended MCP Servers
Journey fit
Cross-file breakage shows up while you are actively building and letting agents edit many files—before you have full test coverage or production monitoring. Agent-tooling is the shelf for MCP servers that change how coding agents understand and navigate your codebase, not just one API integration.
How it compares
Repo code-graph MCP for navigation, not a hosted browser automation or cloud deployment plugin.
Common Questions / FAQ
Who is Lenspr for?
Solo developers using Claude Code, Cursor, or Codex on real codebases where AI-assisted edits span packages, services, or shared libraries.
When should I use Lenspr?
Use it during active build work—large refactors, feature flags across modules, or renaming APIs—when you need the agent to see graph edges before changing files.
How do I add Lenspr to my agent?
Install the lenspr package from PyPI, configure your MCP client to launch the stdio server from that environment, and point it at your project root per the GitHub README.