Docmancer: MCP server, setup and security

What Docmancer does

According to its repository: “Local-only MCP server for source-attributed Markdown memory and documentation retrieval.”

An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Docmancer is listed under Coding agents, a category of 151 servers in the directory, where it ranks #67 by stars.

Topics declared by the repository: ai-agents, claude-code, codex, devtool, agent-memory, ai-memory.

Installing and connecting Docmancer

Distribution modes declared in the official MCP registry:

• PyPI package (Python, started with uvx or pip)

Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: Python.

Security: what to check

An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.

None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Docmancer. That does not replace reading the code.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on March 29, 2026, the docmancer/docmancer repository has 133 stars and 12 forks, with 4 open issues. It has more stars than 71% of the servers in the directory. Last change 2 months ago. Version published in the registry: 0.9.17 (August 13, 2026).

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.