Open source

A doctrine you can read beats one you have to take on faith.

Cartographer is being built open-core. The short version: the parts that ask for your trust will be open to inspection; the parts that ask for your money are convenience, not secrets about you.

The stance

What will be open

The trust doctrine and its enforcement — the constraint layer that runs filters before weights, the consent state machine with its terminal refusal, the display gates that refuse receipt-less statements, the binding never-scored list — together with the tests that prove each rule. If this site claims the code enforces something, the plan is that you can go read the code and the test that holds it there.

What stays hosted

The conveniences around the core: managed hosting and sync, connected accounts, the operational budget and scheduling around mining, support. Paying is for not having to run it yourself — never for finding out what it does.

The repository

Where the code is

The repository opens with launch. Until then, this page — and the principles it summarizes — is the public record, and the waitlist is where you'll hear when the code is readable.

Join the waitlist

Connect an agent

One server, any MCP client.

Cartographer serves its map to agents over the Model Context Protocol — a local process speaking MCP over stdio, run from the repository root with its graph store up (docker compose up -d --wait falkordb). The configurations below reference the build's real entrypoint, published now so that connecting a client is a paste, not a project, the day the repository opens. Interpreter paths use the POSIX venv layout (.venv/bin/python); the same venv on Windows exposes .venv/Scripts/python.exe.

The labels are honest: verified means the exact invocation answered a standard MCP handshake against the running server on 2026-07-07, during the pass that built this page; expected-compatible means the client speaks standard MCP but has not been connected to this server yet.

Any MCP client

Verified

The raw server command, as verified on Windows on 2026-07-07: it answered an MCP initialize and listed its tools. On POSIX the interpreter is .venv/bin/python.

cd /path/to/cartographer
docker compose up -d --wait falkordb
.venv/Scripts/python -m mcpserver.server

Claude Code

Expected-compatible

The build's own documented install command, verbatim — the machine it was built on runs Windows; swap in .venv/bin/python on POSIX. Run from the repository root.

cd /path/to/cartographer
claude mcp add cartographer -- .venv/Scripts/python.exe -m mcpserver.server

Claude Desktop

Expected-compatible

A local server entry in claude_desktop_config.json — command and args only: this client sets no working directory, and the build's documented install doesn't need one. A hosted connector URL is planned; none exists yet.

{
  "mcpServers": {
    "cartographer": {
      "command": "/path/to/cartographer/.venv/bin/python",
      "args": ["-m", "mcpserver.server"]
    }
  }
}

Cursor

Expected-compatible

Project-level .cursor/mcp.json — command and args only, as with Claude Desktop.

{
  "mcpServers": {
    "cartographer": {
      "command": "/path/to/cartographer/.venv/bin/python",
      "args": ["-m", "mcpserver.server"]
    }
  }
}

Gemini CLI

Expected-compatible

mcpServers entry in ~/.gemini/settings.json. Gemini CLI honors cwd, so the working directory is pinned to the repository root here.

{
  "mcpServers": {
    "cartographer": {
      "command": "/path/to/cartographer/.venv/bin/python",
      "args": ["-m", "mcpserver.server"],
      "cwd": "/path/to/cartographer"
    }
  }
}

OpenCode-style CLIs

Expected-compatible

Generic local-server MCP config for CLI agents; adapt the key names to your client.

{
  "mcp": {
    "cartographer": {
      "type": "local",
      "command": ["/path/to/cartographer/.venv/bin/python", "-m", "mcpserver.server"],
      "enabled": true
    }
  }
}

A site about machine-readable context should be machine-readable itself: this one ships llms.txt and agents.json — the latter describes the tool surface behind these configurations, with shipped and planned tools labeled as exactly that.