lodekeep

Persistent, curated memory for every AI, in one command. Vendor-neutral: Claude, ChatGPT, Cursor, Grok, Codex, any MCP client.

Lodekeep gives Claude a long-term memory that follows you across Claude Desktop, Claude Code, and every other MCP surface. This package is the tiny installer + local bridge: it connects your machine to your Lodekeep account and runs a thin stdio ↔ hosted proxy. No database, no API keys, and no secrets ever run locally — every tool call is forwarded to https://lodekeep.com with your personal key.

Quick start

npx lodekeep connect

Paste your MCP install token or API key from lodekeep.com → Settings when prompted. The installer validates the key, stores it locally with locked-down permissions, and auto-configures Claude Desktop (and offers to add it to Claude Code). Restart Claude and it remembers.

Try it: in any chat say remember: we use tabs, not spaces, then in a new chat ask what are my formatting preferences?.

Commands

| Command | What it does | | --- | --- | | npx lodekeep connect | Validate your key, store it, and configure Claude Desktop / Claude Code. | | npx lodekeep status | Show whether your stored key is still valid and which account it belongs to. | | npx lodekeep disconnect | Remove the Lodekeep entry from Claude and delete the stored key. | | npx lodekeep serve | Run the local MCP bridge. You normally never run this by hand — Claude launches it. |

connect options

| Flag | Meaning | | --- | --- | | --key <token> | Provide the key non-interactively (else you are prompted). | | --api-url <url> | Point at a different backend (default https://lodekeep.com). | | --yes, -y | Non-interactive: accept prompts and add to Claude Code. | | --no-claude-code | Skip the Claude Code step. | | --no-claude-desktop | Skip the Claude Desktop step. |

Where your key is stored

Your key lives in ~/.lodekeep/config.json with 0600 permissions (readable only by you). It is not written into the Claude config in plaintext — the Claude entry is just:

{
  "mcpServers": {
    "lodekeep": { "command": "npx", "args": ["-y", "lodekeep", "serve"] }
  }
}

The serve bridge reads the key from ~/.lodekeep/config.json at launch.

Manual setup (no installer)

Prefer to configure Claude yourself? Add this to your claude_desktop_config.json and provide the key via env:

{
  "mcpServers": {
    "lodekeep": {
      "command": "npx",
      "args": ["-y", "lodekeep", "serve"],
      "env": {
        "LODEKEEP_API_KEY": "<your key from Settings>",
        "LODEKEEP_API_URL": "https://lodekeep.com"
      }
    }
  }
}

Claude Code:

claude mcp add lodekeep -s user -- npx -y lodekeep serve

Privacy

No telemetry. The installer talks only to the backend you point it at (https://lodekeep.com by default).

License

MIT