Source: https://mnemoverse.com/docs/api/claude-apps Content revision: 4243e5df5f5b90b08b0087186b9c1143415bda1201db0b81242a02b7973062f1 Updated: 2026-11-05T15:38:16Z # 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](https://mnemoverse.com/docs/api/claude) instead — it sets up differently. ## Connect in one click **[Connect to Claude](https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Mnemoverse&connectorUrl=https%3A%2F%2Fmcp.mnemoverse.com%2Fmcp)** The link opens the **Add custom connector** dialog on claude.ai with the name `Mnemoverse` and the URL `https://mcp.mnemoverse.com/mcp` filled in. Review both, click **Add**, and sign in when the browser opens. The link only fills in the form: nothing is added until you confirm. Anthropic documents remote connectors across Desktop, web and mobile. Verify the connection in the app and account you actually use; this platform capability is not a fresh Mnemoverse runtime test. Free plans allow one custom connector. By hand, the same steps are **Customize → Connectors**, then **+** and **Add custom connector**, and paste `https://mcp.mnemoverse.com/mcp`. Sources, read 2026-09-29: Anthropic's [directory and custom connectors](https://claude.com/docs/connectors/building/directory-vs-custom) for the link, which "opens the dialog with the name and URL prefilled"; the [custom-connector guide](https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp) for the steps and "Free users are limited to one custom connector."; and [desktop and web connectors](https://support.claude.com/en/articles/11725091-when-to-use-desktop-and-web-connectors): "Remote connectors work across all Claude surfaces." ## Claude Desktop **Recommended — OAuth connector (no API key).** Use [Connect to Claude](https://mnemoverse.com/docs/api/claude-apps#connect-in-one-click) above, or in the Claude Desktop app: **Customize → Connectors**, then **+** and **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](https://mnemoverse.com/docs/api/remote-mcp-server) for how the OAuth sign-in works and the tools it exposes, and Anthropic's [custom-connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) 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, [Connect to Claude](https://mnemoverse.com/docs/api/claude-apps#connect-in-one-click) fills in the connector for you. By hand, connectors are added under **Customize → Connectors** — **+**, **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, check the active account and connector before drawing conclusions about stored data: see [what an account switch does to your connection](https://mnemoverse.com/docs/api/remote-mcp-server#what-an-account-switch-does-to-your-connection). **Plan & org notes** Custom connectors are available on the Free, Pro, Max, Team and Enterprise plans, and Free plans allow one custom connector. On Team/Enterprise an admin may need to enable the connector for the org first. Check Anthropic's [connector docs](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) for current plan limits before relying on it. ## Mobile Anthropic documents remote connectors across Claude apps on the same account, so connect on Desktop or claude.ai first. A fresh Mnemoverse installation and memory operation on mobile have not been verified here; run the check below in your actual mobile conversation. See Anthropic's note on [desktop vs web connectors](https://support.claude.com/en/articles/11725091-when-to-use-desktop-and-web-connectors). ## Verify connection and memory Ask the assistant to call `memory_stats` with `{}` on the Mnemoverse server you connected. A successful stats result confirms **read access**, including an empty account with zero memories. Listed tools, an empty response, or an error do not confirm the connection. Report the actual authentication, permission or transport error instead of claiming success. If the user only wanted to connect, stop here; do not write a test memory. To verify saving when the user requests it: 1. Use a harmless fact that is true and that the user actually wants saved. Ask the assistant to save that fact with `memory_write`; do not invent a deployment rule, preference or contact for a test. 2. Check the actual `memory_write` result. Report a new save only if it says the memory was stored. If it refuses the write or returns an error, report that outcome; do not claim that a new memory was saved. 3. Start a new conversation, or use another connected tool on the same Mnemoverse account. Ask the assistant to call `memory_read` for the topic without repeating the fact. Confirm recall only when the actual tool result contains the saved fact. An ordinary answer from chat context or a local rules file is not proof. The stats check alone does not verify writes. If the user already requested a memory task, continue that task after the check and verify its own results. For ongoing use, you can add memory rules to **Instructions for Claude** in Settings: [Make Your Agent Use Memory](https://mnemoverse.com/docs/api/agent-memory#set-up-your-agent-add-the-memory-rules). They guide later recall; they are not required for the explicit check above. If this setup saved you time, a [GitHub star](https://github.com/mnemoverse/mcp-memory-server) helps the next builder find it. ## Which Claude integration is this? Use the **hosted connector** above for browser sign-in. These three items are separate; a listing for one does not establish the review or installation status of another: | Item | Connection or package | What was observed | | --- | --- | --- | | Hosted remote MCP connector | Add `https://mcp.mnemoverse.com/mcp` as a custom connector and sign in with OAuth. | This guide's recommended connection. Adding a custom connector does not confirm approval of its separate directory submission. | | [MCP Memory](https://claude.com/marketplace/connectors/mcp-memory) | Older local Desktop extension; it requires a Mnemoverse API key for tool calls. | On 22 October 2026, a Windows Desktop account showed **Verified Desktop Extension**, version **0.8.3**. | | Mnemoverse Memory | Community Plugin sourced from [mnemoverse/claude-plugin](https://github.com/mnemoverse/claude-plugin). | In the same account on 22 October 2026, **Settings → Extensions → Browse** showed **Community Plugin**, version **1.0.2**, **2 skills, 3 commands, 1 connector**, and the label **“from Anthropic Directory”**. The `mnemoverse` connector was **Not added**. | Those Desktop card details are dated observations in one account. They do not confirm the Community Plugin's current version, the hosted connector's directory approval, or successful installation or OAuth. No fresh mobile runtime test is established by those observations. ## Tools Over the remote connector Claude gets 11 tools: the core memory tools such as `memory_read` and `memory_write`, the Beta shared-room tools for [Rooms](https://mnemoverse.com/docs/api/rooms), and `vault_list`, which returns the aliases of stored secrets and never their values. The [Remote MCP Server](https://mnemoverse.com/docs/api/remote-mcp-server#tools) page lists every one. Full parameters are in the [API Reference](https://mnemoverse.com/docs/api/reference); the connector surface is described on the [Remote MCP Server](https://mnemoverse.com/docs/api/remote-mcp-server) page. ## Related - [Claude Code](https://mnemoverse.com/docs/api/claude) — the CLI (`claude mcp add`), a different setup - [Remote MCP Server](https://mnemoverse.com/docs/api/remote-mcp-server) — how the one-click OAuth connector works - [Make Your Agent Use Memory](https://mnemoverse.com/docs/api/agent-memory) — the memory rules for Instructions for Claude - [Agent Setup](https://mnemoverse.com/docs/api/agent-setup) — which auth method for which client, at a glance - [Rooms](https://mnemoverse.com/docs/api/rooms) — share a memory pool across accounts (Beta) - [API Reference](https://mnemoverse.com/docs/api/reference) — tool parameters and the REST API