Weavatrix MCP server

Weavatrix — native MCP repository intelligence

Part of the Weavatrix ecosystem: evidence infrastructure for AI software agents.

Give your coding agent repository evidence before it starts guessing.

Weavatrix is the native MCP product that answers the questions agents otherwise invent: what breaks if this file changes, who consumes this n8n field, whether an MCP schema still accepts yesterday’s request, which viem call sites follow an ABI layout change, and whether .weavatrix/architecture.json still holds. 67 read-only operations, one revision-bound graph, no LSP and no prompt pack.

Codex, Claude Code, Cursor, and Grok get impact, architecture, APIs, Git history, duplicates, dead code, search, semantic links, temporal memory, exported n8n workflows (n8n), Dify YAML apps (dify), Agent Plugins/Skills/MCP catalogs (agent), Mermaid flowcharts (diagram), and Web3 ABI/consumer impact (web3_*). Those parsers are domains on Weavatrix Core, not new MCP products. Dedicated pages: n8n · Dify · parsers.

It does not answer from a larger grep or an invented confidence score. Every bounded result can carry the repository revision, file, line, extractor, evidence kind, and confidence that produced it.

Adjacent MCP tools (not this host)

This repository is the stdio MCP host and plugin pack. It pins weavatrix-rust. It does not grow a second indexer, and it does not compete with the engine crate for the same README story.

The host’s unique job is transport: profiles, watching, npm/crate distributions, and the 67-tool catalog over one engine session. Measured engine times live in weavatrix-rust benchmarks, not here.

Ecosystem place (UNDERSTAND)

Weavatrix (this) — code facts
        │
        ▼
Weavatrix Loom — semantic composition (capabilities, registry, compile → Rust)
        │
        ▼
Realforge — artifact construction (scaffold / package / deploy)

Shortened. The full README is on GitHub.