Vouch — Claude Code MCP server: what it does, how to install
Maintains a Git-tracked knowledge base where agents only propose updates for human approval. Useful when multiple tools or teammates share project documentation.
claude mcp add --env VOUCH_KB_PATH=<VOUCH_KB_PATH> --transport stdio vouch -- uvx vouch-kbWhat Vouch does
Vouch converts project memory into plain files inside a .vouch/ directory. Instead of letting models overwrite notes at will, it forces every edit through a manual review gate. Agents generate YAML claims, but entries become permanent only after a human signs off on them.
The system enforces source checks on every record. When running vouch compile, an LLM organizes raw claims into structured topic pages in Markdown. If an assertion lacks a valid content-hashed source citation, the engine flags it as an error.
Running the tool requires the vouch-kb package from PyPI via uvx or pipx. Teams needing an interactive dashboard can install vouch-kb[web] to spin up a local interface at http://localhost:5173. Without manual sign-off on queued edits, proposed statements never reach the permanent repository log.
What it helps with
- prevent unreviewed model edits in project documentation
- verify content-hashed source citations before updating docs
- compile structured Markdown wiki pages from approved YAML claims
- keep knowledge base changes tracked inside Git commits
Example prompts for the agent
- Check pending claims in
.vouch/and show what needs review - Run
vouch compileto assemble the deployment guide from approved notes - Draft a new YAML claim about our caching policy for human sign-off
How to install Vouch
Platform CLI
claude mcp add --env VOUCH_KB_PATH=<VOUCH_KB_PATH> --transport stdio vouch -- uvx vouch-kbReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from vouch-kb <command>
Platform CLI
codex mcp add vouch --env VOUCH_KB_PATH=<VOUCH_KB_PATH> -- uvx vouch-kbReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from vouch-kb <command>
Config file
{
"mcpServers": {
"vouch": {
"command": "uvx",
"args": [
"vouch-kb"
],
"env": {
"VOUCH_KB_PATH": "<VOUCH_KB_PATH>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from vouch-kb <command>
Config file
{
"servers": {
"vouch": {
"type": "stdio",
"command": "uvx",
"args": [
"vouch-kb"
],
"env": {
"VOUCH_KB_PATH": "<VOUCH_KB_PATH>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from vouch-kb <command>
Platform CLI
gemini mcp add -e VOUCH_KB_PATH=<VOUCH_KB_PATH> vouch uvx vouch-kbReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from vouch-kb <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Vouch
How to install Vouch in Claude Code?
Run claude mcp add vouch -- uvx vouch-kb in your terminal. If you need a custom directory path, run claude mcp add --env VOUCH_KB_PATH=<VOUCH_KB_PATH> --transport stdio vouch -- uvx vouch-kb.
What does Vouch do?
It serves as a Git-native documentation store where LLMs propose facts instead of writing directly. Changes stay uncommitted until approved, keeping project knowledge auditable across team members.
How are verified notes stored?
Everything lives in your project repository under the .vouch/ directory as plain YAML and Markdown files. You can diff changes with standard Git commands and share them via git clone.
