Cartographer MCP Server

Governance MCP server for agent-maintained knowledge bases (OKF): git-backed writes, search, lint.

What the server does

LLM agents forget everything between sessions, and stateless RAG only bolts retrieval onto that amnesia. The alternative is a knowledge base the agent itself builds and maintains over time — but letting an agent loose on a folder of files ends in broken links, lost history, and silent corruption. Cartographer is the governance layer that makes the pattern safe: the agent works the wiki exclusively through MCP tools, and the server enforces every invariant — validation, linking, immutability gates, one git commit per write.

The wiki is grounded in Karpathy's "LLM Wiki" pattern (operating model: knowledge accretes over time, it is not stateless RAG) on top of the OKF substrate (Open Knowledge Format v0.1 by Google Cloud) — each KB is a folder of .md files with YAML frontmatter, self-contained and version-controlled with git. Zero lock-in: the wiki is readable by any tool, including Obsidian and any text editor.

• 🔧 Full MCP tool suite — complete list in docs/control-plane.md
• 📖 Read & navigation — atlas_overview, index_get, concept_read, map_list,
• 🔍 Search — keyword (pure-Go inverted index) plus optional hybrid semantic search via Ollama
• ✍️ Validated writes with optimistic concurrency (if_match / content-hash), including concept_new from KB-owned templates discovered through template_list
• 📎 Concept assets — read, write, list, and delete binary or text dossier files inside expanded concepts
• 🛡️ Governance — deterministic lint (broken link, stale claim, orphan, map contracts), commit_gate,

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.