Docmancer MCP server

by docmancer.dev·dev.docmancer/docmancer·v0.9.17·133 stars

No reviews yet

Local-only MCP server for source-attributed Markdown memory and documentation retrieval.

A89/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A89/100

full report

Adoption

Established

133 stars212 downloads/wk

Reviews

Write one

Nobody has reviewed Docmancer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Docmancer tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings

Code scansource not scanned: tarball over 25MB25/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 82 days ago12/15
Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10

Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Docmancer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 89/100; higher than 80% of 48,255 servers
GitHub stars: 133; more than 95% of 28,688 servers
Downloads a week: 212; more than 76% of 12,191 servers with a package

Install Docmancer in Claude Code, Cursor or VS Code

claude mcp add docmancer -- uvx docmancer

Add to Cursor

What the publisher says

From the Docmancer repository's README, as published. We do not edit it. Read it on GitHub

Docmancer

Your AI coding environment, restored on every machine.

Website  ·  Documentation  ·  Blog  ·  Changelog  ·  Discussions

Your coding agents remember what happened on one machine

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

Your agents already learned this. They just cannot tell each other.

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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Docmancer: common questions

Is Docmancer MCP server safe?: Yes, by our scan: it is graded A (89/100). Read the Docmancer safety report
How do I install Docmancer?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Docmancer need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Docmancer maintained?: The last commit was 83 days ago (2026-08-13). The latest release is v0.9.17.
How does Docmancer compare with other MCP servers?: safety score 89/100 (higher than 80% of 48,255 servers); github stars 133 (more than 95% of 28,688 servers); downloads a week 212 (more than 76% of 12,191 servers with a package). Full comparison.