Lenspr

Name: Lenspr
Author: kyrylopr

@kyrylopr

About Lenspr

Code intelligence MCP server that makes AI coding safer. Builds a dependency graph of your entire codebase so Claude, Cursor, or any MCP client knows what breaks before making changes. 60+ tools for impact analysis, health scoring, dead code detection, and architecture enforcemen

#code-analysis #developer-tools #code-graph #impact-analysis #python #typescript #mcp-server #vibecoding #code-quality #refactoring #claude-code #cursor

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "lenspr": {
      "command": "lenspr",
      "args": [
        "serve",
        "."
      ],
      "env": {}
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Lenspr?

Lenspr is an MCP server that parses your codebase into a dependency graph and gives AI coding assistants 60+ tools to understand the full picture before making changes. It provides impact analysis, health scoring, and context-aware intelligence for AI agents like Claude Code and Cursor. Designed for both individual vibecoders and professional teams, Lenspr runs entirely locally so your code never leaves your machine.

How to use Lenspr?

Install with pip install 'lenspr[all]', then run lenspr init . and lenspr setup . in your project root. Restart your IDE and your AI will have access to lens_* tools. No cloud dependency—everything runs on your machine.

Key features of Lenspr

Dependency graph parsing for complete code context
Health scoring (A to F) for codebase fitness
Impact analysis before any AI edit
Dead code detection across your project
NFR checks for security and error handling
Architecture rule enforcement per edit

Use cases of Lenspr

AI-powered refactoring with full caller-callee awareness
Preventing blind edits that break distant dependencies
Enforcing architecture boundaries (e.g., frontend must not import backend)
Detecting dead functions and untested code during development

FAQ from Lenspr

How is Lenspr different from a linter?

A linter says "function is too long." Lenspr says "function is too long AND 15 other functions depend on it AND it has 0 tests AND handles authentication—if it breaks, login, registration, and every admin page stop working."