Docmancer — Claude Code MCP server: what it does, how to install
Docmancer — an MCP server for Claude Code, Codex and other agents: indexes memory, rules and session history from local directories and consolidates them into a single Markdown store.
MIT ★ 133 updated 2026-08-13
claude mcp add docmancer -- uvx docmancerWhat Docmancer does
Runs on Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and others via MCP. Scans CLAUDE.md, AGENTS.md, Cursor rules, memory directories and session transcripts, extracts decisions and constraints, builds proposals with citations from the original sessions and waits for approval before writing. Stores everything in local Markdown with stable docmancer://memory/<id> addresses that survive file moves. Search uses SQLite FTS5 and a bundled embedding model with no network calls or API keys.
The docmancer backup --local command creates an encrypted archive with agent history, memory and configuration, excluding .env files, authentication stores and caches. Restore skips identical files, applies verified configuration only and isolates divergent sessions. Requires Python 3.11 or later and pipx (or uv).
What it helps with
- merge context from Claude Code, Codex, Cursor into one store
- find decisions and rules already written into agent memory
- move agent sessions and memory to a new machine with conflict detection
- get an answer with transcript citations instead of a paraphrase
- keep agent memory in Markdown files you can read and commit
Example prompts for the agent
- Show what Docmancer can protect during backup:
docmancer backup --dry-run - Create a local archive with agent history:
docmancer backup --local --to ~/Backups/agents.dmbak - Find in agent history why we moved off Railway
How to install Docmancer
Platform CLI
claude mcp add docmancer -- uvx docmanceruvx runs the command named after the package; if the README names another one, use uvx --from docmancer <command>
Platform CLI
codex mcp add docmancer -- uvx docmanceruvx runs the command named after the package; if the README names another one, use uvx --from docmancer <command>
Config file
{
"mcpServers": {
"docmancer": {
"command": "uvx",
"args": [
"docmancer"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from docmancer <command>
Config file
{
"servers": {
"docmancer": {
"type": "stdio",
"command": "uvx",
"args": [
"docmancer"
]
}
}
}uvx runs the command named after the package; if the README names another one, use uvx --from docmancer <command>
Platform CLI
gemini mcp add docmancer uvx docmanceruvx runs the command named after the package; if the README names another one, use uvx --from docmancer <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 Docmancer
How to install Docmancer in Claude Code?
Run claude mcp add docmancer -- uvx docmancer, then docmancer setup. The setup command finds all agents, shows a change plan and indexes memory after you confirm.
What does Docmancer do?
Indexes memory, rules and session history from Claude Code, Codex, Cursor and other agents, builds a single Markdown store and gives agents access to shared project context. Answers are built from local records with citations from session transcripts.
Which data does Docmancer exclude from backup?
Excludes .env files, authentication stores, literal MCP environment values, caches, logs, telemetry and machine keys. Restore applies verified configuration only and isolates divergent sessions.