Skip to main content
ClaudeWave

An Open Source Intelligent Codebase Visualizer for you and your agents for javascript, reactjs, nextjs and nodejs for easy PR review, fast Onboarding and deep architectural understanding

MCP ServersOfficial Registry35 stars3 forksTypeScriptAGPL-3.0Updated today
Install in Claude Code / Claude Desktop
Method: NPX · @devlensio/skill
Claude Code CLI
claude mcp add devlensoss -- npx -y @devlensio/skill
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "devlensoss": {
      "command": "npx",
      "args": ["-y", "@devlensio/skill"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

<div align="center">

<img src="assets/logo_1.png" alt="DevLens Logo" width="120" />

# DevLens

**Intelligent codebase visualizer.**

Turn any JavaScript, TypeScript, React, Next.js, or Node.js repo into a living, queryable map — with functional summaries, technical summaries, and security analysis on every node.

[![License: AGPL v3](https://img.shields.io/badge/License-AGPL_v3-blue.svg)](https://www.gnu.org/licenses/agpl-3.0)
[![npm: @devlensio/cli](https://img.shields.io/badge/npm-%40devlensio%2Fcli-cb3837?logo=npm)](https://www.npmjs.com/package/@devlensio/cli)
[![Built with Bun](https://img.shields.io/badge/Built%20with-Bun-f9f1e1?logo=bun)](https://bun.sh)

**[Join the DevLens Cloud Waitlist →](https://devlens.io)**

</div>

---

[![DevLens Demo](assets/image.png)](https://youtu.be/6OMsk8lNv4c?si=wpYF80IcfuJpN_Gf)

<p align="center"><em>Click the image to watch the demo</em></p>

---

## Table of Contents

- [About](#about)
- [Who is this for](#who-is-this-for)
- [Quick Start](#quick-start)
- [The Problem DevLens Solves](#the-problem-devlens-solves)
- [Benchmarks](#benchmarks)
- [Ways to Use DevLens](#ways-to-use-devlens)
  - [Web UI](#web-ui--visual-exploration)
  - [CLI](#cli--terminal-power)
  - [Agent Skill](#agent-skill--ai-powered-understanding)
  - [MCP Server](#mcp-server--for-any-mcp-compatible-ai-agent)
- [Configuration](#configuration)
- [What DevLens Understands](#what-devlens-understands)
- [Repository Layout](#repository-layout)
- [DevLens Cloud](#devlens-cloud)

---

## About

DevLens is a **codebase visualizer** for JavaScript, TypeScript, React, Next.js, and Node.js projects. It builds a typed dependency graph of every component, hook, function, route, and store — with AI-powered summaries on each node — so you can explore, understand, and analyze your architecture in seconds instead of hours.

> **What makes it different?** Instead of reading files one at a time, you (or your AI agent) query the pre-built graph. A node summary costs **~50 tokens** vs **~2,000 tokens** per file.

---

## Who Is This For

### Developers & Teams

- **Onboard new devs in hours, not weeks** — explore the graph instead of spelunking files.
- **Review PRs with full context** — see exactly what depends on each change.
- **Run impact analysis before refactoring** — "what breaks if I change this?"
- **Catch circular deps, god-files, and coupling hotspots** automatically.
- **Keep living documentation** — summaries stay fresh as code changes.

### Engineering Leaders

- **Get a bird's-eye view** of your entire codebase in seconds.
- **Spot architectural debt** before it becomes a crisis.
- **Understand what your team has been building** — even across repos.

### Students & Learners

- **See how real codebases are designed** — layers, patterns, data flow.
- **Understand why things are connected**, not just what each file does.
- **Learn architecture patterns** from production-grade projects.

### AI-Augmented Developers

Your agent burns tokens re-reading files it's seen before. DevLens gives it a graph to query instead.

> **Coming soon — DevLens Cloud:** Shareable graphs your whole team can access, cross-repo navigation, and giving graphical context to your AI agents for smarter code review and analysis — all without running anything locally.

---

## Quick Start

**1. Install**

```bash
npm install -g @devlensio/cli
```

> **No Node.js?** Use the standalone binary installer (no dependencies):
>
> **Linux / macOS:**
> ```bash
> curl -fsSL https://raw.githubusercontent.com/devlensio/devlensOSS/main/scripts/install.sh | sh
> ```
>
> **Windows (PowerShell):**
> ```powershell
> irm https://raw.githubusercontent.com/devlensio/devlensOSS/main/scripts/install.ps1 | iex
> ```
>

**2. Init**

```bash
cd your-project
devlens init
```

This sets up your LLM provider for AI summaries. Don't need AI? Skip this — structural analysis works offline.

**3. Analyze**

```bash
devlens analyze . --summarize
```

This builds a typed dependency graph of every component, hook, function, route, and store — with AI-powered summaries on each node.

**4. Explore**

```bash
devlens overview                  # big picture: framework, stats, central nodes
devlens find-nodes -t ROUTE       # find every route in the app
devlens security                  # see security flags across the codebase
```

---

## The Problem DevLens Solves

AI coding tools let you ship faster than ever — but that speed creates **AI debt**: code merged without understanding, agents re-discovering connections every session, new hires drowning in unfamiliar structure.

DevLens fixes this by pre-building a **typed dependency graph** of your entire codebase. Every node gets:

- **Functional summary** — what business purpose does this serve?
- **Technical summary** — how does it work?
- **Security assessment** — severity + explanation

Armed with this graph, you (or your AI agent) can understand the full architecture in **~50 tokens per node** instead of ~2,000 per file.

---

## Benchmarks

*Tested across real-world tasks — architecture understanding, feature implementation, and bug finding — comparing the same model (DeepSeek V4 Flash, GLM 5.2, Kimi K2.6, Qwen 3.6) with and without DevLens.*

### Architecture Understanding (4 models, full DevLens MCP)

<br /><br />

<div align="center">
<img src="assets/01_arch_metrics.png" alt="Architecture benchmark — cost, tokens, steps comparison" width="90%" />
</div>

<br /><br />

| Metric | Without DevLens | With DevLens | Improvement |
|--------|:--------------:|:------------:|:-----------:|
| Avg cost per query | $0.163 | **$0.075** | **54% cheaper** |
| Avg input tokens | 88,980 | **35,035** | **61% less** |
| Avg output tokens | 9,549 | **3,233** | **66% less** |
| Avg tool steps | 14.3 | **7.8** | **45% faster** |
| Structured architecture output | 50% | **100%** | **2× more reliable** |
| Architectural debt discovered | 0% | **50%** | **Now discoverable** |
| Avg cache hit rate | 75.2% | **83.7%** | **+8.5pp** |

<br /><br />

<div align="center">
<img src="assets/03_arch_savings_per_model.png" alt="Per-model savings" width="70%" />
<br /><br />
<img src="assets/02_arch_cache.png" alt="Cache hit rate comparison" width="70%" />
</div>

<br /><br />

> **Notable:** Even the strongest model (DeepSeek V4 Flash) was **81% cheaper** ($0.0035 vs $0.0185) and used **83% fewer input tokens** with DevLens.

### Feature Implementation & Bug Finding (DeepSeek V4 Flash)

*5 prompts across implementation and debugging tasks — DevLens graph context only (no per-node summaries).*

<br /><br />

<div align="center">
<img src="assets/04_prompt_metrics.png" alt="Prompt benchmark metrics" width="80%" />
</div>

<br /><br />

| Task | Input tokens saved | Cache improvement |
|------|:-----------------:|:-----------------:|
| Continue Watching feature | **24%** less input (56.8k vs 74.9k) | +5.2pp cache |
| Rate Limiting feature | **22%** less input (32.1k vs 41.1k) | +8.3pp cache |
| Error Handling audit | *(comparable)* | Comparable |
| Profile Bug trace | **32%** less input (36.9k vs 54.3k) | Similar |

### Quality Impact (Architecture Task)

<br /><br />

<div align="center">
<img src="assets/09_quality_comparison.png" alt="Quality comparison" width="80%" />
<br /><br />
<img src="assets/08_quality_matrix.png" alt="Quality matrix" width="80%" />
</div>

<br /><br />

When asked to explain a codebase's architecture:

| Capability | Without DevLens | With DevLens |
|-----------|:--------------:|:------------:|
| Produced structured output | 50% | **100%** |
| Referenced specific graph metrics | 0% | **100%** |
| Identified architectural debt | 0% | **50%** |
| Named specific important files | 75% | **100%** |

---

## Ways to Use DevLens

Pick the interface that fits your workflow.

### <img src="assets/web-icon.svg" width="20" style="vertical-align: middle" /> Web UI — Visual Exploration

*For when you want to see your codebase laid out as an interactive graph.*

Open the Web UI, paste your repo path, and explore a force-directed canvas — click any node to see its summaries, callers, callees, and security flags. Search, filter, diff commits across versions.

```bash
git clone https://github.com/devlensio/devlensOSS.git
cd devlensOSS && bun install && bun run dev
```

### <img src="assets/cli-icon.svg" width="20" style="vertical-align: middle" /> CLI (`@devlensio/cli`) — Terminal Power

*For scripts, CI, and when you want answers fast without leaving the terminal.*

```bash
npm install -g @devlensio/cli
```

| Command | Description | Example |
|---------|-------------|---------|
| `devlens analyze .` | Analyze a repository into a DevLens graph | `devlens analyze ./my-app --summarize` |
| `devlens overview` | Big picture — framework, stats, central nodes | `devlens overview` → "Next.js 15, 342 nodes, 12 routes, top node: Layout (9.2)" |
| `devlens blast-radius <nodeId>` | What breaks if I change this? | `devlens blast-radius "src/auth.ts::login"` → "14 dependents affected" |
| `devlens cycles` | Find circular dependencies | `devlens cycles` → Lists every circular import group |
| `devlens find-nodes -t <type>` | Filter nodes by type (ROUTE, COMPONENT, etc.) | `devlens find-nodes -t ROUTE` → Lists all 12 routes |
| `devlens find-nodes --severity high` | Find high-severity security issues | `devlens find-nodes --severity high` → "2 findings in auth module" |
| `devlens diff <from> <to>` | Compare two analyzed commits | `devlens diff abc123 def456` → "Added: AnalyticsTracker, Changed: CheckoutForm" |
| `devlens security` | List every security issue | `devlens security --min-severity high --json` |
| `devlens config` | View configuration with all saved providers | `devlens config` |
| `devlens config set` | Interactive provider configuration with live model fetching | `devlens config set` |
| `devlens config --active <key>` | Switch active provider without re-entering credentials | `devlens config --active openai:deepseek` |
| `devlens config --re
ai-summariesarchitecturecode-analysiscode-visualizationcode-visualization-toolcodebase-visualizationcodebase-visualizerdependency-graphdev-tooldeveloper-toolsgraph-visualizerpr-reviewtoken-reductionvisualization

What people ask about devlensOSS

What is devlensio/devlensOSS?

+

devlensio/devlensOSS is mcp servers for the Claude AI ecosystem. An Open Source Intelligent Codebase Visualizer for you and your agents for javascript, reactjs, nextjs and nodejs for easy PR review, fast Onboarding and deep architectural understanding It has 35 GitHub stars and was last updated today.

How do I install devlensOSS?

+

You can install devlensOSS by cloning the repository (https://github.com/devlensio/devlensOSS) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is devlensio/devlensOSS safe to use?

+

devlensio/devlensOSS has not been audited yet by our security agent. Review the original repository on GitHub before using it in production.

Who maintains devlensio/devlensOSS?

+

devlensio/devlensOSS is maintained by devlensio. The last recorded GitHub activity is from today, with 0 open issues.

Are there alternatives to devlensOSS?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy devlensOSS to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: devlensio/devlensOSS
[![Featured on ClaudeWave](https://claudewave.com/api/badge/devlensio-devlensoss)](https://claudewave.com/repo/devlensio-devlensoss)
<a href="https://claudewave.com/repo/devlensio-devlensoss"><img src="https://claudewave.com/api/badge/devlensio-devlensoss" alt="Featured on ClaudeWave: devlensio/devlensOSS" width="320" height="64" /></a>

More MCP Servers

devlensOSS alternatives