Cartographer

MCP文档知识

提供方 未标注

文档知识 HTTP · 远程 Token 社区 / 第三方 ClaudeCursorVS CodeCline
查看接入方式

一个共享的、基于Git的Markdown维基,供团队的AI代理通过MCP工具读取和扩展。服务器强制执行模式、链接检查、代码检查以及每次写入一个Git提交,因此不同机器和客户端上的代理无法破坏它。它还为每个客户端配置技能、子代理和钩子。

一句话选型结论

按资料字段整理

Cartographer 属于文档知识类 MCP 服务器,HTTP · 远程,Token,可直接接入 Claude、Cursor、VS Code 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式HTTP · 远程 鉴权Token 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

HTTP · 远程 Token
连远程 HTTPS 端点,通常为 Streamable HTTP
npx add-mcp 'https://cartographer-demo.beppetemp.com/mcp'

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Cartographer当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

7.2 KB
来自项目仓库与上游目录的原文,未做删改

Shared memory for your team's AI agents — one wiki they all read and grow, and none of them can break.

What a colleague's agent works out on Monday, yours already knows on Tuesday — even on another client.

Cartographer is the platform: Meridian (server), Compass (client), Atlas (web UI) and Surveyor (maintenance agent), one Go binary, git underneath.

Claude Code, Codex, OpenCode, Kiro, Antigravity, Crush, Copilot, Pi, Cline and any MCP client.

Drawn by the Atlas's own graph engine.

Why

AI agents start every session from zero, and on a team every colleague's agent starts from its own
zero: what one learns stays on that person's machine, in that client. The usual fixes each solve
a third of the problem:

  • RAG retrieves, but nothing accumulates — the agent never gets to write down what it learned.
  • A folder of Markdown the agent edits freely ends in broken links, lost history and silent
    corruption.
  • Skills, subagents and instructions get hand-copied into .claude/, .codex/, .kiro/…
    and drift apart on every machine.

Cartographer puts all three in one place: your agents read and grow a knowledge base only
through MCP tools
, behind a server that enforces the rules, and the same knowledge base carries
how your agents are set up.

Try it now

Open the static Atlas demo: a finished, read-only
knowledge base on astronomy, with nothing to install. To give your agents a knowledge base of their own,
see the Quick start.

The four components

One binary, deployed as four components that you pick from:

Component What it is Command Deploy it when
Meridian The server: the only writer of a KB, MCP over HTTP (or stdio for one local client) cartographer serve Always: it holds the KBs
Surveyor A headless maintenance agent for one perimeter of KBs cartographer surveyor You want the wiki kept in order without a person asking
Atlas The read-only web UI, served by Meridian none (a switch of Meridian) You want to see the graph, the changes and the findings
Compass The client next to the agent: configures every agent client, syncs, runs the local bridge, hosts client plugins cartographer connect, sync On every machine where an agent runs

Three rules hold them together: components talk only through documented interfaces; each does only its
job; you deploy only what you need. Details: docs/deployment.md.

Four scenarios: everyone on their own laptop, a team on one server, any MCP agent with no client, and all of them around one KB. See the deployment scenarios.

What you get

  • 🧠 Memory that compounds (Meridian). A wiki the agent builds over time (Karpathy's LLM Wiki pattern): plain Markdown + YAML in a git repository you own, readable in Obsidian or any editor. No lock-in.
  • 🛡️ Guardrails, not good intentions (Meridian). Agents write only through MCP tools, and Meridian is the only writer of a KB: schema and link checks, lint, optimistic concurrency, one commit per write, a signed audit log. The agent cannot leave the KB broken.
  • 👥 Built for teams (Meridian). Several KBs behind one server, per-KB and per-map access with bearer-token roles, git as the sync layer, conflicts turned into a guided workflow, SOPS-encrypted secrets.
  • 🧩 One KB configures every agent (Compass). Skills, subagents, hooks and instructions live in the KB and reach each agent client in its own format, translated, not copied. Edit once, every machine converges. What each client gets: docs/sync.md.
  • 🗺️ See it all (Atlas). A read-only web UI in the same binary: a living 3D graph, search, what the agents changed, what the KB ships to them, and what needs fixing.

The Atlas, served by Meridian, on a generated demo KB.

  • 🔭 Keeps the wiki in order while nobody is looking (Surveyor). Its tasks ingest from feeds and polled sources, repair and review the KB and write syntheses, through the same MCP tools, with its own model budgets. Recipes: docs/surveyor-recipes.md.

  • 🔌 Extend it with plugins. A plugin is a git repository or a folder that extends every component: clients, skills, subagents, hooks, commands and script tools on Compass; roles and presets on Meridian; recipes and connectors on the Surveyor; branding, views and apps in the Atlas. A client Cartographer does not know yet (a fork, an in-house build) is one plugin away. It is installed with one command, pinned to a commit and enabled only after you approve what it does: docs/plugins.md.

Install and quick start```bash

macOS (Homebrew)

brew install beppetemp/tap/cartographer

Windows (PowerShell; no administrator rights)

irm https://raw.githubusercontent.com/BeppeTemp/cartographer/main/install.ps1 | iex

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


Pre-1.0: breaking changes bump the minor version and are called out in the changelog.
Windows runs natively; WSL is covered in `docs/deployment.md`.

Then, with **git** and an **empty git repository** you own (GitHub, Gitea, any host) to hold your first KB:```bash
cartographer setup    # server, first KB and your agents, in one guided step

setup shows its plan before touching anything, then installs the local service, creates the KB,
connects every agent client it detects and verifies the result. Everything it writes is listed, and
removable, in docs/getting-started.md.
Restart your agent sessions and ask for something worth keeping:

> Explore this repository and write a concept page about its architecture in the wiki.

Then open the Atlas (by default http://127.0.0.1:39273/ui/) and watch the page appear. Next session,
ask something related: the agent finds what it wrote and builds on it.

Your KB stays your git repository: Meridian, the only writer, pushes to the remote you gave it.
Cartographer calls no model itself (only the Surveyor does, if you run one), and on loopback no token
is needed; a shared server uses bearer tokens (docs/transport-auth.md).

Prefer to let your agent install it? Paste this:text 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: `<git remote URL>`

If you are an agent asked to install Cartographer: follow that runbook, not the Quick start.

Documentation

Browsable at beppetemp.github.io/cartographer; the
map is docs/index.md.

  • Getting started — from zero to a working wiki
  • Overview — vision, principles, architecture
  • MCP tools — the full tool API
  • Deployment — components, deployment scenarios, configuration, backup
  • Surveyor recipes and connectors — feed the wiki from your sources
  • Sync — how artifacts reach each agent client
  • Plugins — add clients, commands and MCP tools, approved per version

Contributing

Bugs and ideas go to issues; a
question starts from the FAQ. PRs are welcome: CONTRIBUTING.md
covers building, testing and the PR flow. Cartographer is a personal project maintained on a best-effort basis.
Security reports: SECURITY.md.

License

Apache License 2.0 — see LICENSE.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Cartographer 怎么安装?

在客户端按下面的安装命令接入:npx add-mcp 'https://cartographer-demo.beppetemp.com/mcp'。装完在客户端配置里引用同一个包或端点。

Cartographer 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Cartographer 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Cartographer 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Cartographer 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Cline、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Cartographer 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Cartographer 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Cartographer 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。