Pindoc runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 14 Jul 2026.
Code-pinned team memory for AI coding agents — typed artifacts, MCP-native, self-host.
What the code does
We read the source, 18 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
target := filepath.Join(s.root, clean)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Pindoc
same job, measured the same wayLocal code-memory graph for AI coding agents.
Local long-term memory MCP server (SQLite) for AI coding agents — OpenCode, Claude Code, Cursor
Persistent code memory for AI agents: notes pinned to files and symbols that survive refactors.
Repo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP.
Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Semantic code graph MCP server for coding agents
Shared memory for coding agents. Stop re-explaining your codebase every session.
Pindoc — questions
Answers built from our own checks of this server.