weavatrix 1.2.0

Native MCP server for Weavatrix repository intelligence: 42 read-only evidence, impact, architecture, API, Git, search, semantic, and memory operations
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121

# Getting started

## Requirements

- Node.js 18 or newer for the zero-dependency launcher;
- a supported Windows, macOS, or glibc Linux x64/arm64 platform;
- a local repository the MCP process can read.

No Rust toolchain is required for the npm package.

## Install

Use the prebuilt npm distribution:

```sh
npx -y weavatrix mcp .
```

Or build and install the same product from crates.io:

```sh
cargo install weavatrix
weavatrix mcp .
```

## Run once

Use an explicit path when the MCP client starts outside the repository:

```sh
npx -y weavatrix mcp C:/work/my-project
```

Profiles reduce the advertised surface:

```sh
npx -y weavatrix mcp . --profile=all
npx -y weavatrix mcp . --profile=code
npx -y weavatrix mcp . --profile=seo
```

## Configure Codex

```toml
[mcp_servers.weavatrix]
command = "npx"
args = ["-y", "weavatrix", "mcp", "C:/work/my-project", "--profile=code"]
```

Restart the client after changing its MCP configuration.

## Configure Claude Code

```sh
claude mcp add weavatrix -- \
  npx -y weavatrix mcp C:/work/my-project --profile=code
```

## Verify the native product

```sh
npx -y weavatrix --version
npx -y weavatrix list-tools --profile=code
npx -y weavatrix analyze .
```

Version output reports both identities:

```text
weavatrix 1.2.0 (engine 2.1.1)
```

`analyze` is a diagnostic command. Agent integrations should use `mcp`.

## First useful prompts

```text
Summarize the repository graph and identify its largest communities.
Trace this endpoint from server declaration to all known clients.
Show the bounded impact of changing this symbol.
Verify .weavatrix/architecture.json and explain each new violation.
Find production dead code, excluding tests and generated evidence.
Build a minimal context bundle for this change.
```

## Architecture contracts

Create `.weavatrix/architecture.json` in the analyzed repository, then call
`verify_architecture`. A strict contract can define:

- named components and their paths;
- forbidden dependency directions;
- zero runtime cycles;
- maximum file and function sizes;
- no exceptions and an empty baseline.

Use `explain_architecture_violation` for evidence. An exception proposal is
only a structured suggestion; Weavatrix does not write the contract.

## Freshness

The initial repository is opened before handshake. The first operation performs
an incremental catch-up and starts the native watcher. Later calls refresh only
after relevant filesystem changes.

Use `rebuild_graph` when you explicitly want a full rebuild. Use `open_repo`
to switch the active session to another repository.

## Troubleshooting

- `unknown tool`: the operation is outside the selected profile or was not
  compiled into this product.
- repository open error: pass an existing readable directory.
- no measured coverage: provide a supported coverage artifact; static
  reachability is intentionally not substituted.
- stale client catalog: restart the MCP client after changing profiles or
  product versions.

For Rust embedding, use the protocol-independent
[`weavatrix-rust`](https://docs.rs/weavatrix-rust) crate. Installing that crate
does not install an MCP server.