Always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture.
MCPpedia last refreshed this data
io.github.sergii-ziborov/weavatrix-js is an MCP server that always-fresh local repo graph: LSP-backed impact, Health, dead code, endpoints, architecture. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-sergii-ziborov-weavatrix-js": {
"args": [
"-y",
"weavatrix-js"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This is the JavaScript engine of Weavatrix, continued as weavatrix-js. > The weavatrix npm package ships > weavatrix-rust starting > with 1.0.0; pin weavatrix@0.3.14 or install weavatrix-js to stay on the > JavaScript implementation (including its LSP-assisted TypeScript path).
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'weavatrix-js' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked weavatrix-js against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Transport for TMCP using STDIO
The graph based agentic IDE
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
MCP Security Weekly
Get CVE alerts and security updates for io.github.sergii-ziborov/weavatrix-js and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Part of the Weavatrix ecosystem. This repository preserves the explicit JavaScript engine line.
This is the JavaScript engine of Weavatrix, continued as
weavatrix-js. Theweavatrixnpm package ships the native Rust engine from weavatrix-rust starting with 1.0.0; pinweavatrix@0.3.14or installweavatrix-jsto stay on the JavaScript implementation (including its LSP-assisted TypeScript path).
Local repository intelligence for AI coding agents — understand an application fast, then change it with evidence.
Weavatrix builds a reusable living graph of any local repository — files, symbols, imports, calls, inheritance, Health findings, clone families and Git-history coupling — and gives Claude Code, Codex or any MCP client a bounded map for fast understanding and low repeated context. The same graph then answers change impact, Health, dead-code review, duplicates, history and intended-architecture questions. 34 network-free tools. No repository data leaves your machine.
weavatrix-js — npx -y weavatrix-js <repoRoot>weavatrix-rust is the
pure-Rust read-only MCP and library implementation. Its default build exposes
39 tools, covers the 34 read-only capabilities of this JavaScript line and adds cross-repository Git, vector
search, semantic/SEO linking, and temporal-memory context through independent
MIT crates.
cargo install weavatrix-rust
weavatrix mcp <repoRoot> --profile=code
The Rust engine does not invoke git, rg, Node.js, Python, a language server,
or code from the analyzed repository. Use --profile=all, code, or seo to
expose one bounded view without running duplicate MCP servers. Same-revision
benchmarks and limitations are published in its
benchmark report.
This package is the complete offline engine under the MIT license: it reads and analyzes your code,
initiates no outbound HTTP, and never edits your source. It is the read-only base of a layered stack —
add weavatrix-refactor (Apache-2.0) to apply
hash-verified, reversible edits, or weavatrix-online
for authorized Cloud or self-hosted sync. Each is an optional superset that depends on this core through
a supported extension API; the offline/online split is documented in
docs/adr/0001-v0.3-offline-online-split.md.
Requires Node ≥ 18.
# Claude Code
claude mcp add -s user weavatrix-js -- npx -y weavatrix-js <repoRoot>
# Codex CLI
codex mcp add weavatrix-js -- npx -y weavatrix-js <repoRoot>
# or in ~/.codex/config.toml
[mcp_servers.weavatrix-js]
command = "npx"
args = ["-y", "weavatrix-js", "C:/path/to/repo"]
startup_timeout_sec = 20
tool_timeout_sec = 60
Or run from a clone:
git clone https://github.com/Weavatrix/weavatrix-js
cd weavatrix-js && npm install
claude mcp add -s user weavatrix-js -- node <path-to>/weavatrix-js/bin/weavatrix-mcp.mjs <repoRoot>
<repoRoot> is the repository to start with. Graphs are derived data and never live in your repo:
they are stored in the per-user registry at `~/.weavatrix/graphs/<reposi