AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP unreviewed Apache-2.0 Self-run

Cartographer

mcp-beppetemp-cartographer · by BeppeTemp

MCP governance server in Go for the Agentic Wiki — knowledge that composes, not that you query

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add mcp-beppetemp-cartographer

Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.

Security review

⚠ Flagged

1 finding(s); flagged for manual review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures
  • high Pipes remote content directly into a shell (remote code execution).

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Reliability & compatibility

Not yet reviewed
0 installs to date
no reviews yet
18d ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Cartographer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

 ██████╗ █████╗ ██████╗ ████████╗ ██████╗  ██████╗ ██████╗  █████╗ ██████╗ ██╗  ██╗███████╗██████╗
██╔════╝██╔══██╗██╔══██╗╚══██╔══╝██╔═══██╗██╔════╝ ██╔══██╗██╔══██╗██╔══██╗██║  ██║██╔════╝██╔══██╗
██║     ███████║██████╔╝   ██║   ██║   ██║██║  ███╗██████╔╝███████║██████╔╝███████║█████╗  ██████╔╝
██║     ██╔══██║██╔══██╗   ██║   ██║   ██║██║   ██║██╔══██╗██╔══██║██╔═══╝ ██╔══██║██╔══╝  ██╔══██╗
╚██████╗██║  ██║██║  ██║   ██║   ╚██████╔╝╚██████╔╝██║  ██║██║  ██║██║     ██║  ██║███████╗██║  ██║
 ╚═════╝╚═╝  ╚═╝╚═╝  ╚═╝   ╚═╝    ╚═════╝  ╚═════╝ ╚═╝  ╚═╝╚═╝  ╚═╝╚═╝     ╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝

> MCP governance server in Go for the Agentic Wiki — knowledge that composes, not that you query.

[](https://github.com/BeppeTemp/cartographer/actions/workflows/ci.yml) [](https://github.com/BeppeTemp/cartographer/releases) [](https://goreportcard.com/report/github.com/BeppeTemp/cartographer) [](LICENSE) [](https://go.dev/) []()

> [!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](CHANGELOG.md). 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.

Cartographer offers two complementary profiles:

  • Local Core — single agent, stdio transport, local git. Captures the value of the pattern with

minimal complexity.

  • Server — multi-KB, HTTP + token auth, optional semantic embeddings. For shared and remote

deployments.

Key features

  • 🔧 Full MCP tool suite — complete list in [docs/control-plane.md](docs/control-plane.md)
  • 📖 Read & navigationkb_overview, concept_read, archive_list / dossier_list,

graph_neighbors

  • 🔍 Search — keyword (pure-Go inverted index) plus optional hybrid semantic search via Ollama
  • ✍️ Validated writes with optimistic concurrency (if_match / content-hash)
  • 🛡️ Governance — deterministic lint (broken link, stale claim, orphan), commit_gate,

gate_check, supersede, contradiction tracking

  • 🧬 Transactional git — one commit per write operation; optional synchronization to a remote

(fetch/pull-rebase before and push after every write) — git as a sync layer across multiple instances; agentic conflict handling (concepts flagged degraded + conflicts_list tool + guided skill)

  • 🗂️ Multi-KB with ?kb= routing; bearer-token auth with scopes / RBAC
  • 🔐 Audit log — append-only with hash-chain and Ed25519 signature
  • 🧩 Domain skills (SKILL.md / agentskills.io format) with provisioning and client↔server sync
  • 🔑 Secrets via SOPS — references only, plaintext values never stored
  • ⚙️ Multi-provider configurator — generates MCP config for Claude Code, Codex CLI, Kiro,

OpenCode

  • 📦 OKF-compliant — each KB is an OKF bundle and a standalone git repo, zero lock-in (just git +

Markdown)

Architecture

Cartographer separates a data plane from a control plane:

  • Data plane — the KB itself: OKF Markdown files under data/, organized as

archive → dossier → concept. Plain files + git: history, diff, backup, sharing for free.

  • Control plane — the MCP tools the agent calls. The server applies every invariant (validation,

gates, immutability) so the agent operates safely without direct filesystem access.

The interaction rests on the MCP + Skill + Hook triad: MCP carries data and capabilities, Skills carry procedural know-how loaded on demand, Hooks carry deterministic 0-token automation.

flowchart LR
    A["🤖 Agent (LLM)only via MCP — never touches files"]
    S["CartographerGo MCP serverinvariants enforced server-side"]
    KB[("KBMarkdown + git")]
    R[("remote git")]
    A -- "MCP tools" --> S
    S -- "bounded reads" --> A
    S -- "one commitper write" --> KB
    KB -. "sync in/out" .-> R

Install

# macOS (Homebrew)
brew install beppetemp/tap/cartographer

# Linux / macOS without Homebrew
curl -fsSL https://raw.githubusercontent.com/BeppeTemp/cartographer/main/install.sh | sh

# From source (Go 1.26+)
go install github.com/BeppeTemp/cartographer/cmd/cartographer@latest

Agent-driven install

Give an agent this prompt to install Cartographer, mount its first KB, connect itself, and verify the setup:

Set up Cartographer on this machine by following
https://raw.githubusercontent.com/BeppeTemp/cartographer/main/docs/agent-install.md
My first knowledge base is at: ``

Quick start

The primary path is four commands: install the binary, run it as a native service, create your first KB, and connect an agent client to it.

brew install beppetemp/tap/cartographer   # or curl install.sh, or `go install` (see Install above)
cartographer service install              # generates config, installs and starts the service
cartographer kb create              # scaffolds a KB in the service's data dir
cartographer connect                      # connects an agent client (Claude Code, OpenCode, Codex, Kiro)

cartographer kb create prints how to get the server to pick up the new KB (cartographer service restart, or --restart to do it and wait for it automatically); service install itself hints at kb create if it starts with no KB mounted yet.

connect with no flags in a TTY opens an interactive form (server URL, server name, token env var, auth) instead of the flag defaults; pass --no-input to force the non-interactive behavior. Once connected:

cartographer status   # drift check and client/server version check after upgrades; exit 0 in-sync / 1 drift / 2 error
cartographer sync     # re-apply after drift

For local stdio use (a single KB, no service, typically for development) or a manually-configured HTTP server, see serve --kb --init in docs/deployment.md — the native-service path above covers everyday use.

Configuration

| Environment variable | Default | Description | |---|---|---| | CARTOGRAPHER_KB | — | KB path(s) (single, or multiple comma-separated) | | CARTOGRAPHER_DATA | — | Directory whose subfolders are auto-discovered KBs | | CARTOGRAPHER_HTTP | — | HTTP address (e.g. :8080). Absent = stdio only | | CARTOGRAPHER_AUTH | auto | true / false / unset (auto on HTTP) | | CARTOGRAPHER_TOKENS | — | Comma-separated bearer tokens | | CARTOGRAPHER_GIT_AUTOCOMMIT | true | One git commit per write operation | | CARTOGRAPHER_GIT_SYNC | true | fetch/pull-rebase + push on origin around each write | | CARTOGRAPHER_OLLAMA | — | Ollama server URL for semantic search | | CARTOGRAPHER_OLLAMA_MODEL | nomic-embed-text | Ollama embedding model | | CARTOGRAPHER_AUDIT_LOG | — | Audit log file path | | CARTOGRAPHER_AUDIT_KEY | — | Ed25519 key for audit signing |

Full list with CLI flags and defaults → [docs/deployment.md](docs/deployment.md).

Building and testing

make build         # → bin/cartographer
make test          # Unit tests (go test ./...)
make smoke         # stdio smoke test
make smoke-http    # operator-level HTTP smoke test (creates temp KBs via curl)
make e2e           # agent-level E2E tests with headless OpenCode (9 scenarios)
make e2e-quick     # CRUD scenario only

The E2E harness drives OpenCode in headless mode as a real agent against a local server, using a deliberately economical model as a clarity gate: if a cheap model can complete the mandates, the system is clear enough for production. It needs an OpenAI-compatible endpoint (E2E_LLM_BASE_URL); full strategy → [docs/testing.md](docs/testing.md).

Project structure

cmd/
  cartographer/main.go      # Entry point: subcommand dispatch (serve/version/help/agents/connect/status/sync)
  cartographer/serve.go     # Server: flags + env vars + YAML config, stdio/HTTP
  cartographer/tui.go       # Interactive dashboard (no-args, TTY)
internal/
  config/                   # Server YAML config (flag > env > YAML > default)
  okf/                      # OKF primitives: ConceptID, frontmatter, content-hash
  kb/                       # Data plane: Open, Init, Read/WriteConcept, Validate
  kb/graph.go               # Graph navigation: ExtractLinks, GraphNeighbors
  kb/gate.go                # CommitGate
  kb/gitsync.go             # Transactional git: lock, commit, sync in/out
  kb/conflicts.go           # Conflict registry, MarkDegraded
  mcpserver/                # MCP server: stdio, HTTP handler, MultiKBServer, tools (split by domain)
  mcpserver/gitwrap.go      # Write wrapper: lock + commit + sync
  search/                   # Pure-Go inverted index
  sqlindex/                 # Persisted SQLite index: FTS5 trigram + embedding cache
  lint/                     # Deterministic lint
  gitx/                     # git wrapper: commit, rebase, push, fetch, stash
  audit/                    # Audit log: JSONL hash-chain + Ed25519
  auth/                     # TokenStore, middleware, RBAC, scopes
  embed/                    # Embedder interface + Ollama adapter + vector store
  skill/                    # SKILL.md loader and validator (agentskills.io)
  sops/                     # SOPS decryption wrapper
  configurator/             # Multi-provider adapters, HTTP-only (Claude Code, Codex, Kiro, OpenCode)
  provisioning/             # Manifest, lock (v1/v2 multi-provider), diff, apply — client↔server sync
  agents/                   # Detect() installed agent CLIs on this machine
  clientconfig/             # .cartographer.yaml (server URL, connected agents)
  client/                   # Minimal MCP client (JSON-RPC over HTTP) for the client subcommands
docs/                       # Full documentation (see docs/index.md)
test/e2e/                   # Agent-level E2E harness

Documentation

The full index lives in [docs/index.md](docs/index.md). Main entry points:

  • [docs/overview.md](docs/overview.md) — vision, guiding principles, architecture
  • [docs/data-plane.md](docs/data-plane.md) — KB model, hierarchy, OKF
  • [docs/control-plane.md](docs/control-plane.md) — Go server, MCP tool API
  • [docs/concurrency.md](docs/concurrency.md) — single-writer, git sync, conflicts
  • [docs/deployment.md](docs/deployment.md) — topologies (local service / k8s / multi-server), backup, env vars

Contributing

Issues and PRs are welcome — see [CONTRIBUTING.md](CONTRIBUTING.md) for the build/test loop, the PR flow (squash-merge, conventional titles, docs updated in the same PR), and how to find your way around the codebase. Cartographer is a personal project maintained on a best-effort basis: no response-time SLA. For security reports, see [SECURITY.md](SECURITY.md).

License

Released under the Apache License 2.0. See [LICENSE](LICENSE).

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.