Cursor Persistent Memory

Cursor's context window resets between sessions and doesn't share anything with the other tools in your stack. Rohrpost plugs in over MCP and gives Cursor a knowledge base it can share with Claude Code, Claude Desktop, and VS Code — one memory, every tool, on your own hardware if you want it there.

Download the binary

Log in to app.rohrpost.ioand download rohrpost-mcp for your platform from the Downloadstab, or build it from source:

git clone https://codeberg.org/ftieben/rohrpost.io
cd rohrpost.io
cargo build --release --bin rohrpost-mcp
# binary is at target/release/rohrpost-mcp

chmod +x rohrpost-mcp-*
mv rohrpost-mcp-* ~/.local/bin/rohrpost-mcp

Configure

Create .cursor/mcp.json in your project root to scope Rohrpost to that project (recommended — matches Rohrpost's per-tenant model), or configure it globally inCursor Settings → MCP:

{
  "mcpServers": {
    "rohrpost": {
      "command": "/path/to/rohrpost-mcp",
      "env": {
        "ROHRPOST_GATEWAY_URL": "https://app.rohrpost.io",
        "ROHRPOST_API_KEY": "rp_your_api_key"
      }
    }
  }
}

Self-hosting instead? Swap ROHRPOST_GATEWAY_URL forhttp://localhost:7878 (or wherever your gateway is reachable). Get your API key from the API Keys tab of your admin panel.

Reload the Cursor window (Cmd/Ctrl+Shift+P → "Reload Window") after adding or editing .cursor/mcp.json — Cursor doesn't watch it live.

Verify it's working

Open Cursor Settings → MCP and confirm rohrpost shows a green/connected status with its tools listed. Then, in a chat, ask the agent to store a fact about your project and recall it in a new chat — a working setup answers from memory instead of asking again.

For best results, add a short instruction to your Cursor rules (.cursor/rules or project instructions) telling the agent to call rohrpost_recall at the start of a task and rohrpost_ingest when it makes a durable decision — see theMCP tips section for example prompt instructions.

Troubleshooting

Server shows red/disconnected in Settings → MCP

Check the command path is absolute and the binary is executable. Cursor runs the command in a minimal environment — don't rely on your shell's PATH or aliases; use the full path to the binary.

Tools don't appear in chat

Reload the window after any config change. If it's still missing, check Cursor's MCP logs (Settings → MCP → the server's log icon) for a startup error from rohrpost-mcp — usually a bad gateway URL or an expired/revoked API key.

Project-scoped vs. global config

If you work across multiple codebases, prefer per-project .cursor/mcp.json with a different Rohrpost tenant (and API key) per project — this matches Rohrpost's tenant isolation model and keeps knowledge from one codebase out of another's recall results.