beppetemp/cartographer — explained in plain English
Analysis updated 2026-05-18
Give an AI coding agent a persistent, versioned knowledge base it can grow across sessions.
Run a shared team wiki that multiple agents write to safely over HTTP.
Keep an audit trail of every change an agent makes to its own notes.
| beppetemp/cartographer | d4l3k/turtle | jakecoffman/rest | |
|---|---|---|---|
| Stars | 8 | 8 | 8 |
| Language | Go | Go | Go |
| Last pushed | — | 2018-01-27 | 2021-05-21 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 4/5 | 2/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs Go 1.26+ or a prebuilt binary, plus git, semantic search needs a separate Ollama server.
Cartographer is a Go based server that acts as a governance layer for what its author calls an Agentic Wiki. The idea is that an AI agent should be able to build and maintain its own knowledge base over time instead of relying only on retrieval that has no memory between sessions. The problem with letting an agent write directly to files is that things break: links go stale, history gets lost, and content can get silently corrupted. Cartographer solves this by sitting between the agent and the files. The agent never touches the wiki's files directly. Instead it talks to Cartographer through the Model Context Protocol, known as MCP, and the server enforces rules such as validating writes, checking links, and committing every change to git one at a time. The wiki itself is just a folder of Markdown files with YAML frontmatter, following an open format called OKF, so it can still be opened in any editor or in Obsidian, with no lock-in to Cartographer itself. There are two ways to run it. Local Core is meant for a single agent using a local connection and local git, keeping things simple. The Server profile supports multiple knowledge bases at once over HTTP, with token based authentication and optional semantic search powered by Ollama. Other features include a read and search toolset for browsing the wiki, an audit log that is cryptographically signed and cannot be edited after the fact, support for syncing a wiki to a remote git repository automatically, and a configurator that can set up MCP connections for tools like Claude Code, Codex CLI, Kiro, and OpenCode. It installs through Homebrew, a shell script, or directly with the Go toolchain if you have Go 1.26 or newer. Once installed, a single command starts the server pointed at a knowledge base folder, either for local use or as an HTTP service. The project is licensed under Apache 2.0. It is explicitly labeled as beta software, so its tools and configuration may still change before a stable 1.0 release.
A Go MCP server that lets an AI agent safely build and maintain its own Markdown knowledge base over time, enforcing validation and git commits.
Mainly Go. The stack also includes Go, MCP, Git.
Use freely for any purpose, including commercial use, as long as you include the license and note any changes you made.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.