dev.docmancer/docmancer is an MCP server that local-only MCP server for source-attributed Markdown memory and documentation retrieval. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 62/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dev-docmancer-docmancer": {
"args": [
"docmancer"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Your AI coding environment, restored on every machine.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'docmancer' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked docmancer against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in writing
MCP server for document format conversion using pandoc.
This is an MCP server that allows you to directly download transcripts of YouTube videos.
Scrape, crawl, and map websites to Markdown or JSON via local CLI.
Any URL to clean, LLM-ready Markdown for RAG. Strips ads, nav, and boilerplate.
MCP Security Weekly
Get CVE alerts and security updates for dev.docmancer/docmancer and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Your AI coding environment, restored on every machine.
Website · Documentation · Blog · Changelog · Discussions
Agent backup and restore are development-preview commands. Local encrypted archives are available now. Managed Cloud snapshots remain gated on migration and recovery acceptance.
Docmancer securely restores their sessions, memory, and setup, then makes the useful project context available to every agent you use.
Claude Code and Codex can search the files they already wrote on one machine. A normal dotfile tool can copy directories. Neither gives you an agent-aware, secret-stripped backup with structural verification, project mapping, conflict quarantine, and a reviewed path from raw history to shared project memory.
Start by seeing what Docmancer can protect:
docmancer backup --dry-run
Create a free passphrase-encrypted local archive:
docmancer backup --local --to ~/Backups/agents.dmbak
On a new machine, close Claude Code and Codex and preview the restore:
docmancer restore ~/Backups/agents.dmbak --dry-run
docmancer restore ~/Backups/agents.dmbak
Docmancer restores missing history, skips identical files, merges only safe configuration, and quarantines divergent sessions. It never copies authentication stores, .env files, literal MCP environment values, caches, logs, telemetry, or machine keys.
After backup or restore, local consolidation finds durable decisions and constraints in the protected histories. Every proposal links to exact transcript evidence and waits for review:
docmancer consolidate
docmancer consolidate --review PROPOSAL_ID
docmancer consolidate --approve PROPOSAL_ID
Claude Code knows why you moved off Railway. Codex learned your migration convention. Cursor is still following a rule you overruled two months ago. Each agent wrote something down, none of them agree, and none of it is anywhere you can read.
That knowledge is real, and it is already on your disk. It is sitting in CLAUDE.md files, AGENTS.md files, Cursor rules, agent memory directories, and session history, in a different place and a different format for every tool you use.
Docmancer is built around two questions, in this order: