MnemoverseDocs

Appearance

Install by host ​

Mnemoverse is a hosted memory service for AI agents. Every host on this page reaches the same memory: a fact saved from one tool is recalled in every other tool connected to the same account. The difference between hosts is only packaging and sign-in.

There are three ways a host gets the memory:

  1. A plugin repository. mnemoverse/claude-plugin carries an Agent Plugins 1.0.0 manifest (plugin.json and mcp.json at the repository root), a Claude Code manifest (.claude-plugin/plugin.json and .claude-plugin/marketplace.json), and a Kimi Code manifest (kimi.plugin.json). Hosts that read any of these formats install it straight from GitHub. The plugin points at the hosted server https://mcp.mnemoverse.com/mcp: first use opens a browser sign-in (OAuth 2.1 with PKCE), and there is no API key to paste.
  2. A host-native package. The Cursor plugin, the Gemini CLI extension, the VS Code extension and the Claude Desktop .mcpb bundle from the mcp-memory-server releases.
  3. A plain MCP entry. The remote URL https://mcp.mnemoverse.com/mcp in any client that can complete a browser sign-in, or the local package npx -y @mnemoverse/mcp-memory-server@latest with an API key from console.mnemoverse.com (free tier, no credit card). Both paths are on Quick Setup.

Every path exposes the same ten tools: memory_write, memory_read, memory_list_recent, memory_feedback, memory_stats, four shared-room tools (memory_create_room, memory_invite_to_room, memory_join_room, memory_list_rooms) and vault_list (aliases only, never values).

How to read the Status column

Shipped means the package or manifest is published by Mnemoverse and the install path is on its own documentation page. From host documentation, not verified live means the command or steps are copied from that host's own documentation as read on 2026-09-20, and Mnemoverse has not yet run them end to end on that host. If a step does not behave as written, write to support@mnemoverse.com with the host name and version.

Summary ​

HostFormSign-inStatus
Claude Codeplugin from mnemoverse/claude-pluginbrowser, no keyShipped
Claude Desktop.mcpb bundle, or a custom connectorAPI key in the bundle settings; connector: browser, no keyShipped
Cursormnemoverse/cursor-plugin in the local plugins folder, or mcp.jsonbrowser, no keyShipped (plugin), local install steps from host documentation
VS Code and Copilot Chatextension from the Marketplace, or the Agent Plugin from sourcebrowser, no keyShipped (extension); Agent Plugin from host documentation
GitHub Copilot CLIcopilot plugin install mnemoverse/claude-pluginbrowser, no keyFrom host documentation, not verified live
Gemini CLIgemini extensions install from mnemoverse/gemini-extensionbrowser, no keyShipped
Kimi Code/plugins install from mnemoverse/claude-plugin (kimi.plugin.json)browser, no keyShipped manifest; install line from host documentation
ChatGPT and Codexremote MCP server entrybrowser, no keyFrom host documentation, not verified live
Kiropower imported from the GitHub URLbrowser, no keyFrom host documentation, not verified live
Hermes Agenthermes plugins install mnemoverse/claude-pluginbrowser, no keyFrom host documentation, not verified live
OpenClawbundle from the repositorybrowser, no keyFrom host documentation, not verified live
Grokplugin folder under ~/.grok/plugins/browser, no keyFrom host documentation, not verified live
NanoClawtemplate stamped from templates/browser, no keyFrom host documentation, not verified live
Windsurf, Cline, Zed and any MCP clientremote URL or npx packagebrowser, or API keyShipped

Claude Code ​

/plugin marketplace add mnemoverse/claude-plugin
/plugin install mnemoverse@mnemoverse

Then run /mcp, select mnemoverse and choose Authenticate. The browser opens once; sign in and grant the scopes. Updates arrive with /plugin marketplace update mnemoverse.

What you get: the ten tools from the hosted server, three commands (/mnemoverse:remember, /mnemoverse:recall, /mnemoverse:memory-status) and two skills (agent-memory-discipline, setup).

Source: plugin README and Claude Code plugin marketplaces, read 2026-09-20. Without the plugin, the one-line alternative is on the Claude Code page.

Claude Desktop ​

Two paths.

Custom connector, no key. Settings, then Connectors, then Add custom connector, paste https://mcp.mnemoverse.com/mcp, sign in when the browser opens. Details on the Remote MCP page.

Desktop bundle, API key. Download mnemoverse-memory.mcpb from the latest release of mcp-memory-server. In Claude Desktop open Settings, then Extensions, then Advanced settings, find the Extension Developer section, click Install Extension… and select the file. The bundle runs the local server as a node process launched by Claude Desktop and reads your mk_live_ key from the extension settings, so this path needs a key from console.mnemoverse.com.

Source: Getting started with local MCP servers on Claude Desktop and the mcp-memory-server README, read 2026-09-20.

Cursor ​

Cursor loads two plugin formats from the local plugins folder: Agent Plugins (root plugin.json) and Cursor Plugins (.cursor-plugin/plugin.json). Both Mnemoverse repositories qualify; the Cursor one also ships a rule file.

git clone https://github.com/mnemoverse/cursor-plugin ~/.cursor/plugins/local/mnemoverse

Restart Cursor, or run Developer: Reload Window. The first memory call opens the browser sign-in; Cursor's cursor:// callback is on the sign-in allowlist.

What you get: the hosted server, the agent-memory-discipline rule and skill.

Keyless alternatives without cloning: the Mnemoverse Memory extension on Open VSX, or a remote server entry { "mcpServers": { "mnemoverse": { "url": "https://mcp.mnemoverse.com/mcp" } } } in .cursor/mcp.json. With an API key, the npx entry on the Cursor page.

Cursor Marketplace: the plugin is not listed there yet. Per Cursor's documentation, marketplace plugins are submitted through the Cursor team and reviewed manually.

Source: Cursor plugins (section on local testing: "put either plugin format in ~/.cursor/plugins/local"), read 2026-09-20. Local install steps: from host documentation, not verified live.

VS Code and Copilot Chat ​

Extension (recommended). Install Mnemoverse Memory from the Marketplace, or from a terminal:

code --install-extension Mnemoverse.mnemoverse-vscode

Click Sign In, approve in the browser, done. Works in Copilot Chat Agent Mode (VS Code 1.102 or later). Full page: VS Code and Copilot Chat.

Agent Plugin from source. With the chat.plugins.enabled setting on, run Chat: Install Plugin From Source from the Command Palette and enter:

https://github.com/mnemoverse/claude-plugin

VS Code clones the repository, detects the Agent Plugins 1.0 $schema in plugin.json, loads skills/ and starts the server from mcp.json when the plugin is enabled. To browse it as a marketplace instead, add "chat.plugins.marketplaces": ["mnemoverse/claude-plugin"] to your settings and open the Extensions view with @agentPlugins in the search field.

Source: Agent plugins in VS Code (sections "Install a plugin from source", "Configure plugin marketplaces", "Plugin formats"), read 2026-09-20. Agent Plugin path: from host documentation, not verified live.

GitHub Copilot CLI ​

Copilot CLI installs a plugin from the root of a GitHub repository by OWNER/REPO:

copilot plugin install mnemoverse/claude-plugin

Or register the repository as a marketplace first, then install by name:

copilot plugin marketplace add mnemoverse/claude-plugin
copilot plugin install mnemoverse@mnemoverse

Inside a session the same commands are /plugin marketplace add mnemoverse/claude-plugin and /plugin install mnemoverse@mnemoverse. copilot plugin list shows what is installed; copilot plugin update mnemoverse updates it.

Source: Copilot CLI plugin reference (table "Plugin specification for install command") and Finding and installing plugins, read 2026-09-20. From host documentation, not verified live: in particular, how Copilot CLI runs the browser sign-in for a plugin-bundled remote server has not been checked.

Gemini CLI ​

gemini extensions install https://github.com/mnemoverse/gemini-extension

The first memory call opens a browser sign-in on a localhost callback. /extensions inside Gemini CLI lists what is installed, /mcp shows the server state, gemini extensions update mnemoverse-memory updates it.

What you get: the hosted server plus a GEMINI.md with the recall-before-acting discipline.

Source: extension README, Gemini CLI extensions and the extensions command reference for update, read 2026-09-20.

Kimi Code ​

Kimi Code installs a plugin from a GitHub repository URL and reads kimi.plugin.json at the plugin root. Inside Kimi Code:

/plugins install https://github.com/mnemoverse/claude-plugin
/reload

Kimi installs the latest release of the repository (v1.0.0, which carries kimi.plugin.json). /plugins info mnemoverse shows the manifest, the remote server and the commands; /plugins mcp enable mnemoverse mnemoverse re-enables the server if it was switched off.

What you get: the hosted server, the three commands and the two skills.

Source: Kimi Code plugins (sections "Installing from GitHub", "Plugin Manifest", "MCP Servers in Plugins"), read 2026-09-20. Install line from host documentation, not verified live.

ChatGPT and Codex ​

Codex CLI. Add the hosted server as a remote MCP server and sign in:

codex mcp add mnemoverse --url https://mcp.mnemoverse.com/mcp
codex mcp login mnemoverse

Codex picks the OAuth client registration method itself: CIMD when the authorization server advertises it, otherwise Dynamic Client Registration, which the Mnemoverse sign-in supports for loopback callbacks. To force one method for a single login: codex mcp login mnemoverse --oauth-client-registration dcr.

ChatGPT. Create a connector with the same URL in developer mode; steps and plan requirements on the ChatGPT page.

Plugin directory. OpenAI plugins for ChatGPT and Codex are published through the OpenAI plugin submission portal, not installed from a Git repository, and a Codex marketplace expects .agents/plugins/marketplace.json, which mnemoverse/claude-plugin does not carry today. Until a listing exists, use the MCP entry above.

Source: Codex MCP and Package your plugin, read 2026-09-20. From host documentation, not verified live.

Kiro ​

Kiro powers follow the Agent Plugins specification, so the plugin repository imports as a power:

  1. Open the Powers panel and choose Add Custom Power.
  2. Select Import power from GitHub.
  3. Enter https://github.com/mnemoverse/claude-plugin and click Install.

Kiro reads plugin.json, the skills/ folder and mcp.json; the server activates with the power. Import power from a folder does the same from a local clone.

Source: Install powers and Powers, read 2026-09-20. From host documentation, not verified live: the browser sign-in for a power-bundled remote server has not been checked in Kiro.

Hermes Agent ​

Hermes installs Agent Plugins 1.0.0 packages through its normal plugin workflow; portable packages are disabled until enabled:

hermes plugins install mnemoverse/claude-plugin --no-enable
hermes plugins list
hermes plugins enable <name printed by hermes plugins list>

Hermes loads skills/*/SKILL.md and the streamable-http entry from mcp.json through its native remote MCP client. Skills appear under a namespaced name; skills_list shows the full name.

Source: Build a Hermes Plugin, section "Portable Agent Plugins v1 packages", read 2026-09-20. From host documentation, not verified live: the sign-in flow of Hermes' remote MCP client has not been checked.

OpenClaw ​

OpenClaw installs Agent Plugins, Claude, Codex and Cursor packages as bundles. The repository carries both an Agent Plugins manifest and a Claude marketplace, so either route applies:

# from the Claude marketplace in the repository
openclaw plugins marketplace list https://github.com/mnemoverse/claude-plugin
openclaw plugins install mnemoverse --marketplace https://github.com/mnemoverse/claude-plugin

# or from a local clone, detected as an Agent Plugins bundle
git clone https://github.com/mnemoverse/claude-plugin
openclaw plugins install ./claude-plugin

openclaw plugins list
openclaw plugins inspect mnemoverse

Bundle MCP config is merged into the embedded OpenClaw settings; stdio, streamable-http and sse transports are supported, and the tools are exposed as mnemoverse__memory_read, mnemoverse__memory_write and so on. Installation applies to the running Gateway; mapped features are available in the next session.

Source: Plugin bundles, read 2026-09-20. From host documentation, not verified live: which format OpenClaw picks when both markers are present, and how it runs the browser sign-in, have not been checked.

Grok ​

Grok Bot documents installing packaged skills and connectors from its Marketplace (sidebar, then Your plugins, then Manage plugins and skills); it does not document installing a plugin from a Git repository.

Grok CLI loads plugins from ~/.grok/plugins/, from paths listed under [plugins] paths in ~/.grok/config.toml, and from --plugin-dir <PATH>:

git clone https://github.com/mnemoverse/claude-plugin ~/.grok/plugins/mnemoverse

Source: Skills and routines and Skills, plugins and marketplaces, read 2026-09-20. The xAI page says Grok is "fully compatible with Claude Code with zero configuration needed" and "automatically reads Claude Code marketplaces, plugins, skills, MCPs, agents, hooks, and instruction files", and the repository carries a Claude Code manifest (.claude-plugin/plugin.json). From host documentation, not verified live: how Grok CLI runs the browser sign-in has not been checked.

NanoClaw ​

NanoClaw templates use the Agent Plugins 1.0.0 directory format and are stamped only from the local templates/ directory:

git clone https://github.com/mnemoverse/claude-plugin templates/mnemoverse
ncl groups create --template mnemoverse --name "Mnemoverse memory"

plugin.json, skills/ and the streamable-http entry in mcp.json are loaded; NanoClaw-specific slots (persona, scheduled tasks) stay empty; the display name defaults to the folder name unless --name sets it, as above. Wire the group to a channel afterwards with /manage-channels or ncl wirings create.

Source: Agent Templates, read 2026-09-20. From host documentation, not verified live: NanoClaw runs the agent in a container, and completing a browser sign-in from there has not been checked.

Any other MCP client ​

Windsurf, Cline, Zed, JetBrains, Continue and any client that speaks MCP:

  • Can complete a browser sign-in (loopback callback or an allowlisted host): add the remote server https://mcp.mnemoverse.com/mcp. Which callbacks are accepted is listed on the Remote MCP page.
  • Cannot: run the local package with an API key. Ready config blocks for Claude Desktop, Cursor, VS Code and Windsurf are in the Quick Setup; any other client takes the same command, args and env under the key it uses for MCP servers (Zed calls it context_servers):
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"
      }
    }
  }
}

Verify on any host ​

  1. Ask: Remember that this project uses pnpm, not npm.
  2. Start a new session, in the same tool or in another one connected to the same account, and ask: Which package manager does this project use?

The answer should come from memory. memory_stats (or /mnemoverse:memory-status where the plugin commands exist) shows the count.