Local MCP server/Memory

Cartographer MCP server

Local MCP server

Cartographer is a shared, git-backed Markdown wiki that a team's AI agents read and grow through MCP tools. The server enforces schema, link checks, lint and one git commit per write, and it provisions skills, subagents and hooks into each client. The provider documents a local binary installed with Homebrew or install.ps1 followed by cartographer setup, which mounts your own git remote. The cartographer-demo host is a demonstration instance, not a production service.

No authentication Local install path Reviewed 2026-11-16
About

Where it fits

Teams running shared AI-agent wikis across machines and clients with git-backed writes who need schema enforcement.

  • Read and grow a shared Markdown wiki.
  • Enforce schema and link checks on writes.
  • Provision skills, subagents and hooks into clients.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local binary and setup

Install the binary, then run cartographer setup to mount your own git remote. The provider documents a local service, not a hosted no-auth endpoint. The demo host is a demonstration instance only.

  1. Install the binary

    On macOS use Homebrew. On Windows run the provider's install.ps1 in PowerShell; on Linux use the install script from the repository.

    brew install beppetemp/tap/cartographer
  2. Create an empty git repository for the wiki

    A Cartographer knowledge base is a git repository, so provide an empty repository you own as its remote.

  3. Run setup

    Point setup at your remote and choose the agents to provision.

    cartographer setup --remote <YOUR_GIT_REMOTE> --agents claude --yes

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Cartographer documentationhttps://github.com/BeppeTemp/cartographer/blob/HEAD/docs/getting-started.mdGitHub repositoryhttps://github.com/BeppeTemp/cartographer