MnemoverseDocs

Appearance

Claude Desktop, Web & Mobile ​

Connect Mnemoverse memory to the Claude apps — the Claude Desktop app, claude.ai in your browser, and mobile. For the Claude Code CLI, see Claude Code instead — it sets up differently.

Setup is manual today

The remote connector is live at https://mcp.mnemoverse.com/mcp — what's still rolling out is the one-click directory listing. Until "Mnemoverse" appears in Claude's connector directory, add it manually with the steps below. (Exact menu labels move as Claude updates — the official link in each section always has the current path.)

Make Claude actually use Mnemoverse

Connecting gives Claude the memory tools; it doesn't make Claude use them. By default Claude answers from its own context, not Mnemoverse. Add a one-line standing instruction so it saves to and recalls from Mnemoverse every session: Make Your Agent Use Memory.

Claude Desktop ​

Recommended — one-click OAuth (no API key). In the Claude Desktop app: Settings → Connectors → Add custom connector, paste the URL, and complete the browser sign-in on first use:

text
https://mcp.mnemoverse.com/mcp

No config file, no key to paste. See Remote MCP Server for how the OAuth sign-in works and the tools it exposes, and Anthropic's custom-connector guide for the current exact steps.

Alternative — local config + API key. If you'd rather run the local stdio server, edit the Desktop config file (macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json):

Claude Desktop — add to claude_desktop_config.json:

json
{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY",
        "MNEMOVERSE_API_URL": "https://core.mnemoverse.com/api/v1"
      }
    }
  }
}

Fully quit and reopen Claude Desktop after saving — MCP servers are only picked up on startup. This path needs an API key; the OAuth connector above needs none. The MNEMOVERSE_API_URL in this config is the REST backend the local server calls — do not paste it as a connector URL.

claude.ai (web) ​

In the browser, connectors are added in the Claude Settings → Connectors UI — Add custom connector, paste the same URL, sign in. The web app is remote-only (no local stdio server in a browser), so the OAuth connector is the way in.

If the Mnemoverse tools vanish after you sign out or switch accounts, that is the connector being dropped, not your data: see what an account switch does to your connection.

Plan & org notes

Custom connectors and their availability can depend on your Claude plan, and on Team/Enterprise an admin may need to enable the connector for the org first. Check Anthropic's connector docs for current plan limits before relying on it.

Mobile ​

The Claude mobile apps inherit the connectors on your account — connect once on Desktop or claude.ai, and mobile follows. There's no separate mobile setup. See Anthropic's note on desktop vs web connectors.

If this setup saved you time, a GitHub star helps the next builder find it.

Tools ​

Over the remote connector Claude gets five core memory tools (memory_read, memory_list_recent, memory_stats, memory_write, memory_feedback), plus the four Beta shared-room tools (memory_create_room, memory_invite_to_room, memory_join_room, memory_list_rooms) for Rooms and vault_list, which returns the aliases of stored secrets and never their values: ten tools in total. Full parameters are in the API Reference; the connector surface is described on the Remote MCP Server page.