Skip to main content
ClaudeWave

Your agents break less code and burn fewer tokens — deterministic call/import graph + 27 MCP tools for coding agents. Claude Code plugin & MCP server; zero deps, runs 100% locally.

MCP ServersOfficial Registry0 stars0 forksJavaScriptMITUpdated today
Install in Claude Code / Claude Desktop
Method: NPX · @ghostlygawd/codeweb
Claude Code CLI
claude mcp add codeweb -- npx -y @ghostlygawd/codeweb
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "codeweb": {
      "command": "npx",
      "args": ["-y", "@ghostlygawd/codeweb"]
    }
  }
}
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/brand/banner.png" alt="codeweb — your coding agents grep. codeweb knows." width="100%">

[![CI](https://github.com/GhostlyGawd/codeweb/actions/workflows/ci.yml/badge.svg)](https://github.com/GhostlyGawd/codeweb/actions/workflows/ci.yml)
[![npm](https://img.shields.io/npm/v/%40ghostlygawd%2Fcodeweb?style=flat-square&color=c6f24e)](https://www.npmjs.com/package/@ghostlygawd/codeweb)
[![license: MIT](https://img.shields.io/npm/l/%40ghostlygawd%2Fcodeweb?style=flat-square&color=8a8794)](LICENSE)

**Free & MIT-licensed. Runs entirely on your machine — no account, no server, no telemetry. Reads your code; never executes it.**

**[Website](https://ghostlygawd.github.io/codeweb/)**&nbsp;·&nbsp;[See it in action](#see-it-in-action)&nbsp;·&nbsp;[Install](#install)&nbsp;·&nbsp;[Use](#use)&nbsp;·&nbsp;[For agents (MCP)](#use-it-as-an-mcp-tool)&nbsp;·&nbsp;[How it works](#how-it-works)&nbsp;·&nbsp;[Changelog](CHANGELOG.md)

</div>

**Your agents break less code and burn fewer tokens.**

codeweb reads your code and maps it: every function, and every call between them
(~3 s for 3,000 symbols). It's static analysis — no LLM — so the same code always produces
the same map.

Your coding agents query the map instead of grepping. With grep, agents miss more than half of
a function's real callers ([measured](https://ghostlygawd.github.io/codeweb/research.html)).
They break the code they can't see.

- **For agents:** an MCP server with 27 tools — `codeweb_impact`, `codeweb_callers`,
  `codeweb_find_similar`, and 24 more.
- **Answers:** exact, instant, tiny. Your agents keep their context for the real work.
- **For you:** the supporting view — an interactive map of the whole codebase.

The map also shows things you can't see from inside one file: **duplicated logic, dead code,
hotspots, and tangled domains**.

---

## Try it on your repo

```
cd your-project
npx -y @ghostlygawd/codeweb .
```

Three seconds for 3,000 symbols. Open `.codeweb/report.html` — that's your map.

## See it in action

Every screenshot below is a real generated report of **axios** (274 symbols, 8 domains).
No mockups.

codeweb found 3 real duplications in axios and dismissed 12 false positives —
[the case study](docs/case-study-axios.md). Or
[click around the live map](https://ghostlygawd.github.io/codeweb/demo/).

### Know what an edit breaks — before you write

Click any function in the [living map](https://ghostlygawd.github.io/codeweb/) and its
**blast radius** lights up: everything your change would touch.

Your agents get the same answer over MCP (`codeweb_impact`) — before they write a line.

<div align="center">
<img src="assets/screens/axios-blast-radius.png" alt="codeweb blast radius: AxiosError selected in the axios graph — the selected block wears the accent with a viewfinder frame, blast edges lit across three domains, 27 callers listed in the inspector" width="760">
<br><sub>Selecting <code>AxiosError</code> in axios lights up its <b>27 callers across the domains that depend on it</b> — try it yourself in the <a href="https://ghostlygawd.github.io/codeweb/">living map</a>.</sub>
</div>

### Navigate the whole system

A force-directed map of every symbol, collapsible to domains. Search, drag, zoom, and click any
node to trace what depends on it and what it reaches.

<img src="assets/screens/axios-graph.png" alt="codeweb Graph tab on axios: eight domain blocks (helpers, core, adapters, cancel, defaults, platform) sized by symbol count and linked by stippled call edges" width="100%">

### Findings — stop guessing what to refactor

Ranked **duplication** (the same function defined across many files), the most depended-on
**hotspots** to change with care, and likely-**dead code** — every row clickable to inspect what
calls it and what it calls.

<img src="assets/screens/axios-findings.png" alt="codeweb Findings tab on axios: ranked duplication, hotspots, and likely-dead code, with a clickable detail panel" width="100%">

### See duplication density, and where domains tangle

<table>
<tr>
<td width="50%" valign="top">
<img src="assets/screens/axios-treemap.png" alt="codeweb Treemap on axios: every file sized by lines of code, duplication density carried by a dark-to-lime lightness ramp">
<br><b>Treemap</b> — every file sized by lines of code; the brighter a block, the more of it
is duplicated. The bright blocks are your consolidation targets, at a glance.
</td>
<td width="50%" valign="top">
<img src="assets/screens/axios-matrix.png" alt="codeweb Matrix on axios: a heatmap of call coupling between domains">
<br><b>Matrix</b> — domain-to-domain coupling. A big off-diagonal cell means two domains are
tangled: merge them, or put a clean interface between them.
</td>
</tr>
</table>

<div align="center">
<img src="assets/brand/demo.svg" alt="The codeweb pipeline: extract → cluster → overlap → render, looping" width="840">
<br><sub>The deterministic pipeline, looping: extract → cluster → overlap → render.</sub>
</div>

---

codeweb works at **symbol resolution** — functions, classes, and methods, and the call/import
edges between them. File-level scanners can tell you two *modules* look alike; codeweb tells you
two *functions* are the same work, who calls each, and what merging them would break.

## Benchmarks

- **Finding callers before an edit** — agents found **74%** of a function's real callers with
  codeweb, **44%** with grep, at the same context spend. Missed callers are how edits break
  working code.
- **"What breaks if I change this?"** — one codeweb call, one small answer. Agents grepping
  for the same answer needed ~5 rounds of search and **126× the tokens**, and still guessed.
- **Duplicate detection** — codeweb caught **every planted duplicate with zero false alarms**,
  including renamed copies. Text search catches renamed copies 0% of the time.
- **Trust the answers** — checked against the TypeScript compiler and other independent
  implementations **490,000+ times: zero disagreements**.
- **Speed** — first map in **~3 s** on a 3,000-symbol repo. Queries answer in **~0.1 s**.
  A repo twice the size maps in ~1.3× the time.
- **Known limits** — re-mapping after huge edits is slower than we'd like. On simple tasks,
  agents did fine without codeweb.

Methodology, raw data, and per-claim receipts:
[the evidence ledger](https://ghostlygawd.github.io/codeweb/research.html). Benchmark your own
repo: `npm run bench -- <path>/.codeweb/graph.json`. CI re-runs the performance budgets on
every PR; breaking a published number fails the build.

codeweb also keeps a local tally of what it actually did for you — `npm run stats`:

```
codeweb this month: 41 pre-edit card(s) · 5 card-named caller(s) followed · 2 regression(s) flagged · 120 queries served
```

Considering a dependency? Point codeweb at any repo you don't own yet
(`/codeweb https://github.com/owner/repo`): it clones *read-only*, maps it, and appends an
adoption review. codeweb never executes target code.

## Install

**Free & MIT-licensed. Runs entirely on your machine — no account, no server, no telemetry. Reads
your code; never executes it.**

- Requires **Node.js ≥ 22**. That's it.
- Zero required dependencies — runs on an empty `node_modules`, CI-verified.
- One *optional* wasm grammar (`web-tree-sitter`) sharpens extraction. Never required.
- Releases publish from CI with **npm provenance**. Verify with `npm audit signatures`.

**Using Claude Code?** The plugin adds the `/codeweb` command, ambient pre-edit impact cards, and
all 27 tools:
```
/plugin marketplace add GhostlyGawd/codeweb
/plugin install codeweb
```
Then restart Claude Code so the `/codeweb` command, agents, and skill register.

**Using Cursor, Windsurf, or another MCP agent?** Register the same zero-dependency stdio server
(shown with Claude Code's syntax — swap in your client's add-server command):
```
claude mcp add codeweb -- npx -y -p @ghostlygawd/codeweb codeweb-mcp
```

**Just want the map — no AI involved?** One command, from your project directory:
```
cd your-project
npx -y @ghostlygawd/codeweb .    # ~3 s for 3,000 symbols — then open .codeweb/report.html
```

*Not sure? Run the npx one-liner — it's the whole map, no install, nothing to undo.*

**Or run the engine from a clone:**
```
git clone https://github.com/GhostlyGawd/codeweb.git
node codeweb/scripts/run.mjs /path/to/your/project
```

Every bin, flag, and exit code is tabled in [`docs/cli.md`](docs/cli.md).

**In your editor:** [`editor/vscode-codeweb`](editor/vscode-codeweb/) shows a
**`N callers · blast M`** lens above every mapped symbol. Click through into the report.

## What you can do

Each link lands on full docs, flags, and examples in **[the reference](docs/reference.md)**.

- **Know before you edit** — who calls this, what breaks, does this already exist.
  → [Query the graph](docs/reference.md#query-the-graph-for-agents--humans) ·
  [context & pre-flight](docs/reference.md#agent-tools--context--pre-flight-context-pack-simulate-edit)
- **Gate every edit** — a structural regression verdict on edits, PRs, and architecture rules.
  → [The `diff` verdict](docs/reference.md#guard-agent-edits-diff) ·
  [the PR gate](docs/reference.md#gate-every-pr-github-action) ·
  [the capability suite](docs/reference.md#agent-capability-suite-write--review--optimize)
- **Clean up, ranked** — consolidation and dead-code work, ordered by evidence.
  → [`optimize`](docs/reference.md#advise-consolidations-optimizemjs) ·
  [`hotspots`](docs/reference.md#find-the-hotspots--where-to-refactor-first-hotspotsmjs) ·
  [`campaign`](docs/reference.md#plan-a-whole-optimization-campaign-campaignmjs) ·
  [`trend`](docs/reference.md#track-duplication-over-time-trendmjs)

## Use

```
/codeweb                                  # map the current project
/codeweb src/payments --depth symbol      # deep-dive one subsystem
/codeweb https://github.com/owner/repo    # external review before adopting
/codeweb owner/repo --open                # clone, map,
ai-agentscall-graphclaude-codeclaude-code-plugincode-analysiscode-visualizationcodebase-mapdead-codedependency-graphdeveloper-toolsmcpmcp-servermodel-context-protocolrefactoringstatic-analysis

What people ask about codeweb

What is GhostlyGawd/codeweb?

+

GhostlyGawd/codeweb is mcp servers for the Claude AI ecosystem. Your agents break less code and burn fewer tokens — deterministic call/import graph + 27 MCP tools for coding agents. Claude Code plugin & MCP server; zero deps, runs 100% locally. It has 0 GitHub stars and was last updated today.

How do I install codeweb?

+

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

Is GhostlyGawd/codeweb safe to use?

+

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

Who maintains GhostlyGawd/codeweb?

+

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

Are there alternatives to codeweb?

+

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

Deploy codeweb 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: GhostlyGawd/codeweb
[![Featured on ClaudeWave](https://claudewave.com/api/badge/ghostlygawd-codeweb)](https://claudewave.com/repo/ghostlygawd-codeweb)
<a href="https://claudewave.com/repo/ghostlygawd-codeweb"><img src="https://claudewave.com/api/badge/ghostlygawd-codeweb" alt="Featured on ClaudeWave: GhostlyGawd/codeweb" width="320" height="64" /></a>

More MCP Servers

codeweb alternatives