by mnemoverse
Hosted persistent memory for AI agents over MCP. Tell it a recalled memory helped or misled, and it re-ranks what comes back next. Shared rooms for multi-agent work. One key or OAuth across Claude Code, Cursor, VS Code and ChatGPT. MIT, in the official MCP Registry.
# Add to your Claude Code skills
git clone https://github.com/mnemoverse/mcp-memory-serverGuides for using ai agents skills like mcp-memory-server.
See how mcp-memory-server compares with popular alternatives.
mcp-memory-server is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by mnemoverse. Hosted persistent memory for AI agents over MCP. Tell it a recalled memory helped or misled, and it re-ranks what comes back next. Shared rooms for multi-agent work. One key or OAuth across Claude Code, Cursor, VS Code and ChatGPT. MIT, in the official MCP Registry. It has 29 GitHub stars.
mcp-memory-server's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/mnemoverse/mcp-memory-server" and add it to your Claude Code skills directory (see the Installation section above).
mcp-memory-server is primarily written in TypeScript. It is open-source under mnemoverse on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh mcp-memory-server against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
See comparison
Hosted long-term memory for AI agents over MCP. Two calls cover the basics: memory_write saves a memory, and memory_read finds it again by a natural-language query. Pass domain: "user:<id>" on both to keep each user's memories apart (a namespace inside your account, not a permission boundary). Rating a recalled memory as helpful or misleading re-ranks what comes back next (memory_feedback).
Free plan, no credit card: 1,000 queries a day (reads, writes and feedback combined), 10,000 atoms of storage, 60 requests a minute. Plans and limits: mnemoverse.com/pricing
Using ChatGPT? Install the published Mnemoverse Memory plugin, then complete browser sign-in. Follow the ChatGPT guide to verify the connection; no local package or custom MCP setup is needed for this route.
Other clients: connect with an OAuth sign-in on the hosted endpoint https://mcp.mnemoverse.com/mcp, or run this package locally with an API key. Setup for Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop (formerly Windsurf), Zed, JetBrains, Cline and Gemini CLI is below. Steps for other hosts: mnemoverse.com/docs/api/install-by-host
Shared rooms let several agents work from one memory.
All the MCP tools of this server: memory_write, memory_read, memory_list_recent, memory_feedback, memory_stats, memory_graph, memory_create_room, memory_invite_to_room, memory_join_room, memory_list_rooms and vault_list. Tools says what each one does, and tools.json lists them with their full descriptions.
@mnemoverse/mcp-memory-server is the MIT-licensed MCP server for the hosted Mnemoverse memory engine.
Official sources only: this repository, the npm package @mnemoverse/mcp-memory-server, and the .mcpb attached to this repository's GitHub Releases. A copy of this README elsewhere with its own "Download" button is not ours: please don't run it, and report it to us at support@mnemoverse.com.
Mnemoverse is a hosted memory engine for AI agents, reached over the Model Context Protocol. It stores what your agents learn (decisions, preferences, lessons) and returns it in any connected tool, so one memory follows you across Claude Code, Cursor, VS Code and ChatGPT with one account: an OAuth sign-in on the hosted endpoint, or an API key in a local config.
What is open source here, and what is not. This repository, the MCP server, is MIT, and so is the Python SDK. The memory engine they talk to is a hosted service with a free tier. Self-hosting the engine is available on Enterprise plans by agreement, when security or compliance requirements call for it; by default we run it for you.
Most agent memory today lives in one of three places. Per-tool instruction files (CLAUDE.md, .cursorrules, AGENTS.md) are versioned and readable, each new session reads them again, and a committed file travels with its repository; but a file reaches only the tools that look for its name, so a rule written for Claude Code is not there in a ChatGPT chat. A vector store behind RAG retrieves by similarity, and similarity never changes because advice helped or misled. Local-first memory servers win on privacy and latency, and ask you to run and update the infrastructure yourself. Mnemoverse is the managed, cross-tool option in that landscape: nothing to deploy, one account everywhere, and rating a recalled memory as helpful or misleading re-ranks what comes back next. If you need memory inside your own perimeter, a local-first server is the better choice; this one is hosted by default, with Enterprise self-hosting by agreement.
⭐ If Mnemoverse saves you from re-explaining context to your agents, star the repo. It helps other builders find it.
Create a free account at console.mnemoverse.com (no credit card). Every setup in this section connects to the hosted server https://mcp.mnemoverse.com/mcp and signs you in through the browser, so there is no key to copy. To run this package on your machine with an API key instead, see Local package with an API key.
Claude Code — the hosted server, with a browser sign-in. No API key, nothing to install:
claude mcp add --scope user --transport http mnemoverse https://mcp.mnemoverse.com/mcp
Then start Claude Code, run /mcp, select mnemoverse and choose Authenticate. If the command ran inside a Claude Code session (yours, or Claude ran it for you), that session does not load the new server: exit and start claude again first.
Cursor — click to add the hosted server. Cursor signs you in through the browser, so there is no key to paste:
The button writes {"url": "https://mcp.mnemoverse.com/mcp"} under mnemoverse in ~/.cursor/mcp.json, the global config that covers every project. Then click Connect next to mnemoverse in Cursor's MCP settings (Customize in the sidebar; Cursor Settings → Tools & MCPs in Cursor 3.21.16) and approve in the browser. Cursor runs the sign-in and keeps the token itself.
Any MCP client — a client that adds a remote server by URL and runs the MCP sign-in (OAuth) itself takes https://mcp.mnemoverse.com/mcp. Any other client takes the entry below: mcp-remote, a separate open-source bridge, runs through npx (Node.js 20.18.1 or later), forwards to the same URL and opens the same browser sign-in on first start. Neither way needs a key:
{
"mcpServers": {
"mnemoverse": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.mnemoverse.com/mcp"
]
}
}
}
The bridge keeps its sign-ins in ~/.mcp-auth. If a sign-in gets stuck, its README says to delete that folder and restart the client.
VS Code — the VS Code extension signs in through the browser, with no key to paste: install it and run Mnemoverse: Sign In. Without the extension, add the hosted server to .vscode/mcp.json (VS Code 1.102 or later; VS Code uses servers, not mcpServers). VS Code opens the browser sign-in on first use, and the entry holds no key, so the file is safe to commit:
{
"servers": {
"mnemoverse": {
"type": "http",
"url": "https://mcp.mnemoverse.com/mcp"
}
}
}
Claude Desktop — add the hosted server as a custom connector: Customize → Connectors, then + and Add custom connector, paste https://mcp.mnemoverse.com/mcp and sign in when the browser opens. The connector also works on claude.ai and in the Claude mobile apps; free Claude plans allow one custom connector. To use claude_desktop_config.json instead, add the mcp-remote bridge, which runs through npx (Node.js 20.18.1 or later), and restart Claude Desktop; the bridge opens the same browser sign-in:
{
"mcpServers": {
"mnemoverse": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.mnemoverse.com/mcp"
]
}
}
}
Cline — in the Cline panel, open MCP Servers, then the Remote Servers tab. Enter mnemoverse as the server name and https://mcp.mnemoverse.com/mcp as the URL, choose Streamable HTTP, click Add Server, then click Authenticate on the server's row and sign in in the browser. The same entry by hand, in cline_mcp_settings.json:
{
"mcpServers": {
"mnemoverse": {
"type": "streamableHttp",
"url": "https://mcp.mnemoverse.com/mcp"
}
}
}
Keep "type": "streamableHttp": without it Cline uses the older SSE transport.
Devin Desktop (formerly Windsurf) — add the mcp-remote bridge, which runs through npx (Node.js 20.18.1 or later), to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows) and restart Devi