Docmancer MCP server
{
"mcpServers": {
"docmancer": {
"command": "uvx",
"args": [
"docmancer"
],
"env": {
"PROPOSAL_ID": "<proposal_id>"
}
}
}
}{
"mcpServers": {
"docmancer": {
"command": "uvx",
"args": [
"docmancer"
],
"env": {
"PROPOSAL_ID": "<proposal_id>"
}
}
}
}{
"mcpServers": {
"docmancer": {
"command": "uvx",
"args": [
"docmancer"
],
"env": {
"PROPOSAL_ID": "<proposal_id>"
}
}
}
}{
"servers": {
"docmancer": {
"command": "uvx",
"args": [
"docmancer"
],
"env": {
"PROPOSAL_ID": "${input:proposal_id}"
}
}
},
"inputs": [
{
"id": "proposal_id",
"type": "promptString",
"description": "Proposal id",
"password": true
}
]
}{
"mcpServers": {
"docmancer": {
"command": "uvx",
"args": [
"docmancer"
],
"env": {
"PROPOSAL_ID": "<proposal_id>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx docmancerversion 0.9.17
What it does
Docmancer is a local MCP server that indexes and retrieves documentation and memory from coding agents (Claude Code, Codex, Cursor, Gemini) stored as Markdown files on your machine. It provides source-attributed answers to questions about your project context and decisions, keeping all data local with no telemetry or cloud requirement.
- Ask questions about project decisions and get answers with citations showing which agent's memory or transcript supports each claim.
- Back up and restore coding agent sessions, memory, and configuration across machines with encrypted local archives and conflict detection.
- Consolidate fragmented agent knowledge into shared canonical Markdown documentation that all connected agents can access and reference.
Tools this server exposes
| Tool | Does |
|---|---|
| ask | Query your indexed agent memory and documentation with source attribution for answers. |
| backup | Create encrypted local archives of agent sessions and memory with options for dry-run preview. |
| restore | Restore agent sessions and memory from backup archives on new machines with conflict quarantine and safe merging. |
| consolidate | Extract durable decisions and constraints from agent histories and propose them as reviewed updates to shared memory. |
| web | Open a local web interface to view and manage the current project's memory and documentation. |
| setup | Discover supported coding agents, index their memory and rules, and configure automatic recall integration. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.