Cursor

This guide connects Cursor to MemMesh so your agent remembers across sessions. The path is fully local: install the thinkfleet-memory engine, run one command, and Cursor talks to it over a local stdio MCP server. No API key, no server, no Docker.

Do I need an API key? No. The local engine stores everything in a SQLite file on your machine (~/.thinkfleet-memory/memory.db) and runs on the Free tier out of the box. A managed Mesh Router (hosted) endpoint is coming soon.

Prerequisites

Cursor installed and working.
Node.js 18+ to run the npx installer.
A thinkfleet-memory engine binary. The prebuilt release channel isn’t live yet, so until then set THINKFLEET_BINARY to a binary you have, or build one from source with cargo build --release (see the Quickstart).

Install

npx @thinkfleet/memmesh install --tool cursor

The installer writes the MCP server entry into ~/.cursor/mcp.json and drops the agent teaching skill into ~/.cursor/rules/thinkfleet-memory/ (Cursor loads user-level rules from rules/, not skills/) — preserving any MCP servers you already have. Then restart Cursor so it reloads the config.

💡

Until the binary release channel is live, prefix with your binary path: THINKFLEET_BINARY=/path/to/thinkfleet-memory npx @thinkfleet/memmesh install --tool cursor. Or, with the binary on $PATH, run thinkfleet-memory install --tool cursor directly.

The auto-observe hook is Claude Code-only — Cursor has no event-hook system, so memory is written when the agent explicitly calls the memory tools.

What the installer writes

An entry keyed thinkfleet-memory under mcpServers in ~/.cursor/mcp.json. It’s a stdio server — a command Cursor launches, not a URL:

~/.cursor/mcp.json

{
  "mcpServers": {
    "thinkfleet-memory": {
      "command": "/path/to/thinkfleet-memory",
      "args": ["--db", "/Users/you/.thinkfleet-memory/memory.db", "mcp"]
    }
  }
}

Useful flags:

--dry-run — preview what would be written, change nothing.
--tool <id> — target one tool (repeatable): claude-code, cursor, windsurf, codex. Omit to wire every detected tool.
--skill-only / --mcp-only — install just the skill, or just the MCP config.
--force — install even if the tool isn’t auto-detected.

Verify it works

Restart Cursor, open the MCP settings, and confirm thinkfleet-memory is connected. Or run the diagnostic:

thinkfleet-memory doctor

The memory tools the agent can call are listed in the MCP tool reference.

Remove it

The installer is merge-only, so to remove MemMesh delete the thinkfleet-memory entry under mcpServers in ~/.cursor/mcp.json (and, optionally, the ~/.cursor/rules/thinkfleet-memory/ directory). Your other MCP servers are untouched.

For the full walkthrough and tool reference, see the Claude Code integration — every step is identical except the target tool (and Cursor has no auto-observe hook).

Claude Code Installer & Doctor