Weavatrix Git MCP server
io.github.sergii-ziborov/weavatrix-git·v0.3.1Fast, bounded, read-only Git evidence for local AI coding agents.
0 stars35 downloads/wk
Reviews
Write oneNobody has reviewed Weavatrix Git yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Weavatrix Git tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 20 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Weavatrix Git compares
Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 94/100
- higher than 96% of 1,119 Developer tools servers
- Downloads a week
- 35
- more than 20% of 436 Developer tools servers with a package
Install Weavatrix Git in Claude Code, Cursor or VS Code
Runs npx -y weavatrix-git on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add weavatrix-git -- npx -y weavatrix-git
What the publisher says
From the Weavatrix Git repository's README, as published. We do not edit it. Read it on GitHub
Weavatrix Git
Part of the Weavatrix ecosystem: bounded Git evidence for AI software agents.
weavatrix-git gives AI coding agents fast, bounded, read-only Git evidence. The Rust crate, CLI, MCP server, and npm package are the same contract: parse repository storage directly. No git subprocess, C library, hooks, filters, network access, checkout, or mutation. There is no write API in any surface.
On the checked-in exact-parity benchmark, 1,000 warm history entries took 0.355 ms with Weavatrix, 0.884 ms with gix, and 1.552 ms with libgit2. Across eight repositories, Weavatrix won all five measured p50 contracts. These are engine measurements from release builds; the MCP transport is deliberately not hidden inside the claim.
Run the MCP server
No Rust toolchain is required:
npx -y weavatrix-git@0.3.3 --repository /absolute/path/to/repositoryGeneric stdio client configuration:
{
"mcpServers": {
"weavatrix-git": {
"command": "npx",
"args": [
"-y",
"weavatrix-git@0.3.3",
"--repository",
"/absolute/path/to/repository"
]
}
}
}The npm package contains verified native binaries for Windows x64, Linux x64 and ARM64, and macOS x64 and ARM64. Node only selects and launches the matching binary; repository parsing and MCP handling stay in safe Rust.
Tools for agents
Every list tool returns nextCursor, exact object IDs, and a truncated flag. Non-UTF-8 paths retain their exact bytes in pathHex; display text is never silently presented as exact evidence.
Runtime limits
The MCP binary uses mcport's controlled, Tokio-free runtime:
- 256 KiB maximum request and 1 MiB maximum response;
- four in-flight handlers and bounded request/output queues;
- 30-second handler deadline with cooperative cancellation checks;
- panic isolation and atomic response-overflow errors;
- bounded Git object, history, tree, bitmap, reflog, and index reads;
- optional progress notifications and configurable response batching.
Defaults are suitable for interactive stdio. --help exposes overrides for byte budgets, concurrency, queues, deadline, and batch size. The server writes only newline-delimited UTF-8 JSON-RPC to stdout; diagnostics go to stderr.
Native Cargo installation is also available:
cargo install weavatrix-git --version 0.3.3 --features mcp \
--bin weavatrix-git-mcp
weavatrix-git-mcp --repository /absolute/path/to/repositoryWhy a separate crate?
A scanner discovers files. A code graph models relationships. This crate owns version-control evidence. Keeping that boundary independent lets any Rust application reuse Git intelligence without importing a larger product.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Weavatrix Git: common questions
- Is Weavatrix Git MCP server safe?
- Yes, by our scan: it is graded A (94/100). Read the Weavatrix Git safety report
- How do I install Weavatrix Git?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Weavatrix Git need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Weavatrix Git maintained?
- The last commit was 61 days ago (2026-09-04). The latest release is v0.3.1.
- What can I use instead of Weavatrix Git?
- Servers from other publishers that do the same job: Repowise MCP server, Foremerge MCP server and Mason MCP server.
- How does Weavatrix Git compare with other Developer tools MCP servers?
- safety score 94/100 (higher than 96% of 1,119 Developer tools servers); downloads a week 35 (more than 20% of 436 Developer tools servers with a package). Full comparison.
Alternatives to Weavatrix Git
Same job from other publishers: the closest match first, then the best rated.
RepowiseCodebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.not reviewedEstablishedB- ForemergeCoordinate parallel coding agents, above Gitnot reviewedGrowingA
- MasonEngineering decisions, change impact, documentation audits, and CI evidence for coding assistants.not reviewedGrowingA
- NexusmemLocal-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.not reviewedGrowingA
git-into-gsocEvidence-based GSoC preparation: organizations, repositories, free beginner issues, proposals.not reviewedGrowingA