MCP Overview
MemMesh exposes its memory engine as an MCP server, so any MCP-capable client — Claude Code, Cursor, Windsurf, Codex, or your own — can read and write memory through a standard tool interface.
Transport
The local stdio path is the recommended and currently-shipping default; it needs no API key. A hosted HTTP endpoint is coming soon (see below).
Local (stdio) — recommended, no key
The installer wires your editor to launch the thinkfleet-memory binary directly
as a child process. The config is a command, not a URL — no token, no
Authorization header:
{
"mcpServers": {
"thinkfleet-memory": {
"command": "/path/to/thinkfleet-memory",
"args": ["--db", "/Users/you/.thinkfleet-memory/memory.db", "mcp"]
}
}
}Memory is stored in SQLite at ~/.thinkfleet-memory/memory.db on the Free tier.
See the Quickstart to install, and
Installer & doctor for all options.
Hosted (HTTP)
Mesh Router (hosted) — coming soon. A managed, multi-tenant MCP endpoint with per-project bearer auth is in development. Until it ships, use the local stdio path above, or self-host the HTTP server on your own infrastructure.
Supported clients
The installer knows how to write the right config for each client:
| Client | --tool | Config file |
|---|---|---|
| Claude Code | claude-code | ~/.claude.json (mcpServers map) |
| Cursor | cursor | ~/.cursor/mcp.json (mcpServers map) |
| Windsurf | windsurf | ~/.codeium/windsurf/mcp_config.json (mcpServers map) |
| Codex CLI | codex | ~/.codex/config.toml (mcp_servers table) |
Run the installer with --dry-run to preview the exact entry for any tool
without writing files, then hand-place it into a client not auto-detected.
Tools
The engine exposes a rich set of memory tools over MCP. The primary one is
memory_observe (feed it raw text; the engine decides what to keep); the rest
cover explicit writes, search/recall, prediction, graph reasoning, and
governance. See the full MCP tool reference.
The exact tool set depends on your engine version. Always trust the tool list your connected client reports.
See also
- Installer & doctor — the
npxshim, flags, env knobs, and thedoctordiagnostic. - Claude Code — the recommended, fully worked setup.
- Cursor
- Self-Hosting → Docker — run the optional HTTP server on your own infrastructure.