WEAVATRIX MCP

Give your AI agent blast-radius vision.

Weavatrix builds a code graph of any local repository and serves it to Claude Code & Codex over MCP — change impact, transitive dependents, health audit, clone detection, coverage mapping. 23 tools. One server for every repo on your machine.

Get started Explore the tools ↓
# pre-release — npm package landing soon
$ claude mcp add -s user weavatrix -- npx weavatrix-mcp <graph.json> <repoRoot>

# then, inside Claude Code:
 what breaks if I change the auth middleware?
→ change_impact: 3 changed files map to 9 symbols; 41 dependents in blast radius,
   7 untested hotspots called out — ranked by proximity × connectivity.

The graph your agent is missing

Grep sees text. Weavatrix sees structure: files, symbols, and the imports, calls and inheritance connecting them — built with tree-sitter, no native toolchain.

Change impact

change_impact diffs your branch (staged, unstaged, untracked included) and lists everything that depends on what you touched — with test coverage attached and untested hotspots called out.

Blast radius per symbol

get_dependents walks reverse edges transitively: every caller, importer and subclass that can feel your refactor, ranked by proximity and connectivity.

Health audit

run_audit finds dead code, unused exports, missing and unused dependencies, import cycles, orphans — plus offline OSV vulnerability, typosquat and lockfile-drift checks.

Clone detection

find_duplicates uses MOSS winnowing over method bodies — catches copy-paste even after variables were renamed, not just identical text.

Structural diff

rebuild_graph + graph_diff report the architecture delta of your edits: new module dependencies, broken or introduced cycles, symbols that lost their last caller.

Every repo, one server

open_repo retargets the running server at any local repository and builds missing graphs; list_known_repos shows what's ready. Register once, use everywhere.

JavaScriptTypeScriptTSXPythonGoJavaHTMLCSSRust — roadmap

Local-first, offline by design

Graph queries, audits and clone scans run in-process against local files — your source never leaves your machine. Exactly two tools can touch the network, both in an explicit opt-in capability group: refresh_advisories (queries OSV.dev with package names + versions) and sync_graph (pushes your graph — paths, symbols, edges, never file contents — to an endpoint you configure). Omit the online group at registration and they don't even exist.

Roadmap

The MCP server is free and MIT — forever. The hosted layer comes next.

NOW · FREE · MIT

MCP server

23 tools over your local code graph. Pre-release; npm publish imminent.

PLANNED

CI blast radius

change_impact as a PR comment: what this PR can break, and which of it is untested.