Cartographer
Governance MCP server for agent-maintained knowledge bases (OKF): git-backed writes, search, lint.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.BeppeTemp/cartographer
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
██████╗ █████╗ ██████╗ ████████╗ ██████╗ ██████╗ ██████╗ █████╗ ██████╗ ██╗ ██╗███████╗██████╗
██╔════╝██╔══██╗██╔══██╗╚══██╔══╝██╔═══██╗██╔════╝ ██╔══██╗██╔══██╗██╔══██╗██║ ██║██╔════╝██╔══██╗
██║ ███████║██████╔╝ ██║ ██║ ██║██║ ███╗██████╔╝███████║██████╔╝███████║█████╗ ██████╔╝
██║ ██╔══██║██╔══██╗ ██║ ██║ ██║██║ ██║██╔══██╗██╔══██║██╔═══╝ ██╔══██║██╔══╝ ██╔══██╗
╚██████╗██║ ██║██║ ██║ ██║ ╚██████╔╝╚██████╔╝██║ ██║██║ ██║██║ ██║ ██║███████╗██║ ██║
╚═════╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝
MCP governance server in Go for the Agentic Wiki — knowledge that composes, not that you query.
Warning
Beta software. Cartographer is pre-1.0: the MCP tool surface, CLI and configuration may change between minor releases without a deprecation period. Breaking changes bump the minor version (0.x semantics) and are called out in the changelog. Expect rough edges — bug reports are very welcome.
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.
What is it
Cartographer implements the Agentic Wiki: a persistent knowledge base of interlinked Markdown files that an LLM agent grows and curates by talking to the server over the MCP protocol. The agent never touches the files directly.
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.
One binary, two transports — deployment choices, not separate products: the KB model and the MCP tools are the same on both.
- Local stdio — one client, one KB, no network. The simplest way to run the pattern.
- HTTP server — one or more KBs behind bearer-token auth, as a native user service, a container or a Kubernetes workload. It hands each client the artifacts its KBs define, and lets a team share some KBs while keeping others private.
Two consequences are worth stating on their own, because they are what most of the design is for: the KB configures the agents that read it across every client you use, and it does that for a whole team rather than a single laptop.
Quick start
You need git and an empty git repository you own (GitHub, Gitea, any git host) to be your
first KB's remote: a KB is a git repository, and that remote is what makes it durable and
syncable. sops in PATH is needed only if the KB will hold encrypted values.
From the project's README.