Claude Desktop Memory Setup

Claude Desktop's built-in memory is scoped to that one app. Rohrpost gives it a knowledge base it shares with every other tool you use — Claude Code, Cursor, VS Code — over the same Model Context Protocol Claude Desktop already speaks natively.

Download the binary

Claude Desktop connects to Rohrpost via rohrpost-mcp, a small stdio bridge. If you use the managed service, log in to app.rohrpost.ioand grab the binary for your platform from the Downloads tab. Self-hosting? 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

Make it executable and put it somewhere stable:

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

Configure

Edit claude_desktop_config.json — the file location differs by OS:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/claude/claude_desktop_config.json

Managed (app.rohrpost.io):

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

Self-hosted (local):

{
  "mcpServers": {
    "rohrpost": {
      "command": "/path/to/rohrpost-mcp",
      "env": {
        "ROHRPOST_GATEWAY_URL": "http://localhost:7878",
        "ROHRPOST_API_KEY": "rp_your_api_key"
      }
    }
  }
}

On Windows, use a full path with escaped backslashes or forward slashes in"command" (e.g. "C:/Users/you/rohrpost-mcp.exe"). Get your API key from the API Keys tab of your admin panel — it's scoped to one tenant and starts with rp_.

Restart Claude Desktop completely (quit, not just close the window) after editing the config.

Verify it's working

Open Claude Desktop and check the MCP indicator (hammer/tools icon) shows rohrpostas connected. Then ask it to store something and recall it in a fresh conversation — e.g. "remember that I prefer TypeScript over JavaScript for new projects," then in a new chat, "what's my language preference?" A working connection answers from the stored fact instead of asking you again.

Troubleshooting

Tools icon shows no MCP servers

The config file must be valid JSON — a trailing comma or missing brace silently drops the whole block. Validate it, then fully quit and reopen Claude Desktop (it only reads the config at launch).

"spawn ENOENT" or similar in Claude's logs

The command path is wrong or the binary isn't executable. Use an absolute path, not ~ or a relative path — Claude Desktop doesn't expand shell shortcuts. On macOS/Linux, confirm chmod +x was applied.

Connected, but recall returns nothing

New tenants start with an empty knowledge base. Ingest a few facts manually to confirm the pipeline works end to end, or use the Claude Code plugin's history backfill if this tenant already has data from another client.

Where's the HTTP/remote option?

Today, rohrpost-mcp talks to Claude Desktop over stdio only — you run the binary locally and it connects to your gateway (local or managed) over HTTP under the hood. A hosted HTTP MCP endpoint with OAuth is on the roadmap; until then, the stdio binary works identically whether your gateway is on your own machine or app.rohrpost.io.