Mnemoverse

MCP文档知识

提供方 未标注

文档知识 HTTP · 远程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

为AI代理提供的基于MCP的托管持久内存API;该内存能评估重要性、关联概念,并从结果中学习。

一句话选型结论

按资料字段整理

Mnemoverse 属于文档知识类 MCP 服务器,HTTP · 远程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式HTTP · 远程 鉴权未标注 部署方式远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

HTTP · 远程 未标注
连远程 HTTPS 端点,通常为 Streamable HTTP
claude mcp add mnemoverse -s user \ -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY \ -e MNEMOVERSE_API_URL=https://core.mnemoverse.com/api/v1 \ -- npx -y @mnemoverse/mcp-memory-server@latest

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mnemoverse当前 未标注 HTTP · 远程 远程部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

27.3 KB
来自项目仓库与上游目录的原文,未做删改

Mnemoverse Memory

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:" 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

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, Gemini CLI and ChatGPT is below. Steps for other hosts: mnemoverse.com/docs/api/install-by-host

Shared rooms (beta) let several agents work from one memory.

@mnemoverse/mcp-memory-server is the MIT-licensed MCP server for the hosted Mnemoverse memory engine.

What is Mnemoverse Memory?

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 API key in a local config, or an OAuth sign-in on the hosted endpoint.

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.

How it compares

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.

Quick Start

No key: the hosted endpoint

If your client signs in over OAuth, you do not need a key at all. Create a free account at console.mnemoverse.com (no credit card), then connect the hosted endpoint.

Claude Code:```bash
claude mcp add --scope user --transport http mnemoverse https://mcp.mnemoverse.com/mcp

Then start Claude Code, run `/mcp`, select `mnemoverse` and choose **Authenticate**. A session that was already running when the command ran does not load the new server: exit and start `claude` again first.

Cursor, in `.cursor/mcp.json`:```json
{ "mcpServers": { "mnemoverse": { "url": "https://mcp.mnemoverse.com/mcp" } } }

Claude Desktop, Devin Desktop (formerly Windsurf), VS Code and ChatGPT: Remote MCP setup. The local server below is the other path: it runs on your machine and reads an API key.

1. Get a free API key

Sign up at console.mnemoverse.com — takes 30 seconds, no credit card.

Check the key before you put it in a config. Both forms ask for the key at a masked prompt and never pass it as a command argument, so it lands neither in your shell history nor in the process list.

macOS, Linux, Git Bash:```bash
printf 'Mnemoverse API key: '; read -rs KEY; echo
printf 'X-Api-Key: %s\n' "$KEY" | curl -s -H @- https://core.mnemoverse.com/api/v1/memory/stats; unset KEY


Windows PowerShell 5.1 and PowerShell 7:```powershell
$k = [Net.NetworkCredential]::new('', (Read-Host 'Mnemoverse API key' -AsSecureString)).Password
try { (Invoke-WebRequest https://core.mnemoverse.com/api/v1/memory/stats -Headers @{ 'X-Api-Key' = $k } -UseBasicParsing).Content }
catch { if ($_.ErrorDetails.Message) { $_.ErrorDetails.Message } else { (New-Object IO.StreamReader($_.Exception.Response.GetResponseStream())).ReadToEnd() } }; Remove-Variable k
The output contains What it means
JSON that includes "total_atoms" The key works.
"reason":"placeholder_key" That is the example key from these docs. Create a real one at the console.
"reason":"malformed_key" Not the shape of a key: cut short in the paste, wrapped in quotes, or a different token entirely.
"reason":"invalid_key" The shape is right and no such key exists. Copy it again from the console.
"reason":"revoked_key" The key was revoked and will not work again. Create a new one.
"reason":"missing_key" No key reached the API: what you entered was empty.

In the JSON, reason sits inside the details object (details.reason), next to details.keys_url, the console page where keys are created.

2. Connect to your AI tool

The two canonical setups, Claude Code and Cursor. Each starts with the hosted server: a browser sign-in and no key. Their key-based setups write the key once, at user scope, covering every project; each client further down says where its own config lives. Avoid a per-project config file for a key: it lives inside the repository and can be committed with it, and a key belongs outside:

Claude Code — the hosted server, with a browser sign-in. No API key, nothing to install:```bash
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.

To run the local server with an API key instead (Node.js 18 or later), put your own key in place of `mk_live_YOUR_KEY`. Use one or the other, not both: they share the name `mnemoverse`.```bash
claude mcp add mnemoverse --scope user \
  -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY \
  -e MNEMOVERSE_API_URL=https://core.mnemoverse.com/api/v1 \
  -- npx -y @mnemoverse/mcp-memory-server@latest

On Windows (PowerShell), paste the same command as one line — PowerShell does not read the \ line continuations:```powershell
claude mcp add mnemoverse --scope user -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY -e MNEMOVERSE_API_URL=https://core.mnemoverse.com/api/v1 -- npx -y @mnemoverse/mcp-memory-server@latest


**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.

To run the local server with an API key instead, add the JSON below to `~/.cursor/mcp.json`, merging it with any servers already there, and put your own key in place of `mk_live_YOUR_KEY`. Get one at console.mnemoverse.com. Do not put it in a project-level `.cursor/mcp.json`: that file lives inside the repository and is committed with it unless you exclude it, and this config holds your key. Use one entry or the other, not both: they share the name `mnemoverse`.```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"
      }
    }
  }
}

All other clients — VS Code, Devin Desktop (formerly Windsurf), Zed, JetBrains, Cline

VS Code — the VS Code extension signs in through the browser and needs no key; that's the default path. In VS Code's non-interactive Agent Host mode, servers that prompt for inputs like this one are not started; for unattended use there, put the key in the environment of the process that launches VS Code instead. To wire the MCP server directly instead, add this to .vscode/mcp.json (note: VS Code uses servers, not mcpServers). Never put a literal mk_live_ key in that file — it's committed with the repo. The inputs entry below prompts for the key instead: VS Code masks what you type and stores it in its own secret storage, not in the file:```json
{
"inputs": [
{
"type": "promptString",
"id": "mnemoverse-api-key",
"description": "Mnemoverse API key (starts with mk_live_), for this local package only: the hosted server https://mcp.mnemoverse.com/mcp signs in with OAuth and takes no key. Optional to install and inspect — the server starts and lists its tools without a key; every actual tool call requires one. Get one free in ~30s at https://console.mnemoverse.com",
"password": true
}
],
"servers": {
"mnemoverse": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mnemoverse/mcp-memory-server@latest"
],
"env": {
"MNEMOVERSE_API_KEY": "${input:mnemoverse-api-key}",
"MNEMOVERSE_API_URL": "https://core.mnemoverse.com/api/v1"
}
}
}
}


**Devin Desktop (formerly Windsurf)** — add to `~/.config/devin/mcp_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"
      }
    }
  }
}

More MCP clients — same server, different config file:

Zed — add to ~/.config/zed/settings.json (Zed uses context_servers, and "source": "custom" is required):```json
{
"context_servers": {
"mnemoverse": {
"source": "custom",
"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"
}
}
}
}


**JetBrains** (AI Assistant) — *Settings → Tools → AI Assistant → Model Context Protocol (MCP)*, then paste:```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"
      }
    }
  }
}

Cline — MCP Servers → Configure (or edit cline_mcp_settings.json). Cline reads env values literally, so paste your real key — not a ${VAR} reference:```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"
}
}
}
}


> Why `@latest`? Bare `npx @mnemoverse/mcp-memory-server` is cached indefinitely by npm and stops re-checking the registry. The `@latest` suffix forces a metadata lookup on every Claude Code / Cursor / VS Code session start (~100-300ms), so you always pick up new releases.

> ⚠️ **Restart your AI client** after editing the config. MCP servers are only picked up on client startup.

### 3. Try it — 30 seconds to verify it works

Paste this in your AI chat:

> **"Remember that my favourite TypeScript framework is Hono, and please call `memory_write` to save it."**

Your agent should call `memory_write` and confirm the memory was stored.

Then open a **new chat / new session** (this is the whole point — memory survives restarts), and ask:

> **"What's my favourite TypeScript framework?"**

Your agent should call `memory_read`, find the entry, and answer "Hono". If it does — you're wired up. Write whatever you want next.

If it doesn't remember: check that the client was fully restarted and the config has your real `mk_live_...` key, not the placeholder. On the hosted server there is no key to check; check that the browser sign-in finished (in Cursor, **Connect** next to `mnemoverse`).

> ⭐ If the second session remembered, star the repo. It helps other builders find it.

### 4. Make it a habit

The test above works because you asked the agent to call the tool. In normal work it will not, unless it has a standing instruction that says when to read memory and when to save. The `setup_memory` prompt writes those rules for Claude Code, Claude, Cursor or Codex, and Make Your Agent Use Memory explains where they go and how to confirm the tools work first.

## Tools

| Tool | What it does |
|------|-------------|
| `memory_write` | Store a memory — insight, preference, lesson learned |
| `memory_read` | Search memories by natural language query (optional recency ordering, time bounds, author exclusion) |
| `memory_list_recent` | List newest memories first — no query; `since`/`until` bounds (inclusive) + cursor paging |
| `memory_feedback` | Rate a recalled memory as helpful or misleading, which re-ranks what comes back next |
| `memory_stats` | Check how many memories stored, which domains exist |
| `memory_create_room` | Create a shared memory room; its address works as a `domain` on write/read |
| `memory_invite_to_room` | Mint an invite (code + link) for a room you own; single-use unless `max_uses` allows more |
| `memory_join_room` | Join a shared room with an invite code (`mnvr_...`) |
| `memory_list_rooms` | List rooms you own or joined, with each room's address to use as `domain` |
| `memory_graph` | Read the association edges around given concepts — weight, outcome valence, co-activation count |
| `vault_list` | List Vault secrets by alias and purpose — the secret value is never returned |

### Prompts

Four named prompts for clients that show MCP prompts as commands (Claude Code as `/mcp__mnemoverse__`). None of them calls the API itself: three ask the model to use the tools above, and `setup_memory` hands you rules for your own agent.

| Prompt | Arguments | What it asks for |
|------|------|-------------|
| `recall` | `topic` | Search memory for a topic with `memory_read` and summarize only what comes back |
| `save_insight` | `insight`, optional `domain` | Store an insight with `memory_write` and confirm what was stored |
| `what_do_you_know` | `subject` | A briefing from `memory_read` that flags what is not stored |
| `setup_memory` | optional `host`: `claude-code`, `claude-ai`, `cursor` or `codex` | Memory rules for CLAUDE.md, AGENTS.md, Cursor rules or your chat preferences, and where they go, so your assistant checks and saves memory without being reminded |

### Resources

`memory://item/{memory_id}` opens one saved memory by its id (the `id:` line of a `memory_read` result) for clients that attach MCP resources. It returns the memory's `memory_id`, `content` and `domain` as JSON. It reads your own store only: a memory read from a shared room cannot be opened by id.

### Tool surface stability

`tools/list` is frozen per released version, so a client can save the list it
saw and diff it against what the server serves today, by version.

- **Within a PATCH** (x.y.Z): tool names, argument schemas and the `annotations`
  object of every tool (`title`, `readOnlyHint`, `destructiveHint`,
  `idempotentHint`, `openWorldHint`) do not change. Only text may: descriptions
  and what a tool returns, as the CHANGELOG rules state.
- **Within a MINOR** (x.Y.0): tools and annotation fields may be added, never
  removed or renamed, and no declared annotation field disappears or flips
  silently. Every addition has a line in the CHANGELOG under that version. A
  MINOR may also add an output schema (`outputSchema`, with
  `structuredContent` returned alongside the same text) to a tool that did
  not have one; once declared, that schema's fields are add-only under this
  same rule. Where this server's output schema deliberately differs from the
  hosted connector's, the CHANGELOG entry says so; today that is
  `memory_id` in every output schema, a plain string here and a
  GUID-validated string there (this package's ids are opaque);
  `memory_list_recent`'s `next_cursor`, optional here (absent when the
  service sent a continuation token this client will not pass on) and
  required there; `memory_stats`, which carries five optional fields
  (`episodes`, `prototypes`, `hebbian_edges`, `avg_valence`,
  `avg_importance`) the connector's schema does not declare; the room
  tools (`memory_create_room`, `memory_invite_to_room`, `memory_join_room`,
  `memory_list_rooms`), where several fields the connector marks required
  are optional here (`name`, `scope`, `already_member`, and the invite's
  `code`, `scope`, `room_address` and `expires_at`), because a value core
  did not send is an honest outcome here rather than a placeholder; and
  `memory_list_rooms` and `vault_list`, which drop a row with no usable
  identity (`room_id`, `address`, `role`; `alias`, `context`) from the data,
  reported once on stderr, instead of emitting empty strings into required
  fields; and `memory_read` and `memory_list_recent`, which carry an optional
  `rooms_not_searched` field (the shared rooms an unscoped call did not
  search) that the connector's schemas do not declare yet.
- **Removing or renaming a tool or a tool's input parameter, or dropping or
  renaming a declared annotation field,** is announced one MINOR ahead: the
  tool (or parameter) stays, its description says
  `deprecated since x.y, removed in x.z`, and the change lands only in the
  announced version, with its CHANGELOG line. A renamed parameter is accepted
  under both names until then (0.11 renamed `memory_feedback`'s `atom_ids` to
  `memory_ids`; the old name was removed in 0.13, as announced after 0.12
  shipped sooner than the first announcement assumed). A rename is announced by naming
  both the old and the new name; the version pair alone does not say what a
  client should look for. Because a MINOR may add a field but not remove one, a
  renamed annotation field is declared under both names until the announced
- Any difference between two servers of the same version is a bug. Report it
  with both `tools/list` outputs. One exception, by configuration: a server
  built on the `/shared` entry point may ask for its own noun in the three
  descriptions that name the server (`wording.serverNoun`, below), which
  changes those three description strings and nothing else; tool names,
  input and output schemas and annotations never vary by configuration.

Every `inputSchema` and `outputSchema` is JSON Schema 2020-12, the dialect MCP
assumes when a schema names none, and names none (#189).

The list above is the current surface: eleven tools, each declaring all four hints.
The hosted connector at `mcp.mnemoverse.com/mcp` serves the same surface, registered
from this package at the version it pins. The list itself is published as
`tools.json`, generated from the built server (name, title,
description and annotations per tool); the test suite and the release workflow
fail when it does not list what the server registers, and the `.mcpb` manifest's
tool list is derived from it.

**If the hosted connector stops answering in a session.** A client can keep showing the connector as connected while every call in that session fails with "not connected". Reconnecting it on claude.ai does not revive a session that is already stuck; reconnect from inside the session instead (in Claude Code, `/mcp`, then sign in again). Meanwhile this local server, set up with an API key from the same account as in the Quick Start, reaches the same memory and does not depend on that session's sign-in.

### Building a second MCP server on this package

`@mnemoverse/mcp-memory-server/shared` is the entry point another server registers these same tools from, instead of keeping its own copy (ADR-025, mnemoverse-core). It exports `registerMemoryTools`/`registerMemoryPrompts`/`registerMemoryResources`, the three typed error classes (`ApiError`, `NetworkError`, `UnreadableBodyError`), `MAX_RESULT_CHARS`/`capResult`, and two optional dependencies a hosted deployment injects to speak in its own voice: `wording` (its own server noun and error vocabulary, including an OAuth mode under which no 401 or 403 explanation names an API key) and `writeAuthor` (vouching for the end user behind a write). See `docs/shared.md` for the full contract.

## Use cases

The pattern that pays off first is cross-tool continuity: a decision made while pairing in Claude Code is there when you open Cursor an hour later, and the preference you stated in VS Code holds in a ChatGPT session that evening. Teams use shared rooms the same way — one place where an agent's lessons about a codebase accumulate instead of being re-taught per seat. And rating a recalled memory as helpful or misleading re-ranks what comes back next, which matters once a store grows past what anyone curates by hand.

Concrete things worth writing:

- **User preferences**: "I use dark mode", "I prefer Tailwind over CSS modules"
- **Project context**: "This project uses PostgreSQL + Prisma", "Deploy to Railway"
- **Lessons learned**: "Always run tests before push on this repo"
- **Decisions made**: "We chose REST over GraphQL because of caching simplicity"
- **People & roles**: "Alice is the designer, Bob owns the API"
- **Past mistakes**: "Don't deploy on Fridays — learned this the hard way"

## Universal Memory

The same API key works across all tools. Write a memory in Claude Code — read it in Cursor. Learn something in VS Code — your GPT Custom Action knows it too.```
                    ┌── Claude Code (this MCP server)
                    ├── Cursor (this MCP server)
   Mnemoverse API ──├── VS Code (this MCP server)
   (one memory)     ├── GPT (Custom Actions)
                    ├── Python SDK (pip install mnemoverse)
                    └── REST API (curl)

Configuration

Env Variable Required Default
MNEMOVERSE_API_KEY For every tool call — the server starts and lists its tools without one —
MNEMOVERSE_API_URL No https://core.mnemoverse.com/api/v1

Research behind it

The retrieval model is published: arXiv:2603.08965, accepted at the GRAAI workshop at IEEE WCCI 2026 — it establishes the abstraction-discovery method the memory model builds on. No benchmark figures appear in this README, ours or anyone's: numbers will come with a reproducible run to stand behind, not before.

Links

Setup and reference

  • Documentation
  • Cursor · VS Code · Claude Code · ChatGPT
  • Python SDK
  • API Reference
  • Console (get API key)

Background reading

  • Memory MCP servers compared — thirteen shipping options, with pricing and registry presence
  • How to choose a memory MCP server — the five questions that narrow the field
  • What AI agent memory is — the category explained
  • Is this a vector database? — what makes a memory layer different
  • Shared memory for multi-agent systems — how Rooms work and when to use them

Other ways to install it

The same memory, packaged for hosts that prefer a plugin or an extension over an MCP config block. How each one connects and authenticates differs, so the line below says which is which rather than claiming one flow for all of them.

  • Claude Code plugin — remote endpoint over MCP with an OAuth sign-in, no key to paste. Bundles the agent-memory-discipline skillclaude plugin marketplace add mnemoverse/claude-plugin claude plugin install mnemoverse@mnemoverse
  • Cursor plugin — same remote endpoint, same sign-in
  • Gemini CLI extension — same remote endpoint. gemini extensions install https://github.com/mnemoverse/gemini-extension
  • VS Code extension (VS Code Marketplace, Open VSX, source) — signs in through the browser, with pasting a key kept as a fallback command
  • Desktop extension: manifest.json in this repository is an MCPB manifest. This one is different from the four above: it runs the server as a local node process and reads MNEMOVERSE_API_KEY from the extension settings rather than calling the hosted endpoint. The packaged .mcpb ships with each release

Standing rules, separate from this server

  • agent-memory-discipline — when an agent should recall before acting and save afterward. CC0, backend-neutral, works against any memory store rather than this one. It carries its own marketplace manifest under .claude-plugin/.
  • awesome-agent-memory — a curated index of the category, CC0, including the servers this one competes with

Project

  • GitHub
  • Releases
  • MCP Registry entry
  • Contributing

Privacy Policy

This server sends to the Mnemoverse API (core.mnemoverse.com), authenticated with your API key, what a tool call carries — and nothing else it can see. It does not read your AI client's conversation history, your local files, or anything you don't pass to a memory_* / vault_* tool. Stored memories live under your account; Mnemoverse never sells them and never shares them on its own. The one sharing path is the one you create yourself: inviting someone to a shared room grants their assistant access to that room's memories, bounded by the invite's scope.

What each tool sends:

Tool Data sent
memory_write the content, concepts, and domain you pass
memory_read the query, plus any filters: domain, since/until, exclude_author, top_k, order_by
memory_list_recent the feed filters: domain, since/until, exclude_author, limit, cursor
memory_feedback the memory_ids being rated (sent to the API as atom_ids), the outcome score, and the domain when you pass one (a shared room's address)
memory_create_room the room name and description
memory_invite_to_room the room_id, invite scope, and expiry
memory_join_room the invite code
memory_graph the seeds, plus any of depth, domain, min_weight, limit you pass
memory_stats / memory_list_rooms / vault_list no request body — authenticated GETs

One thing goes out that you did not explicitly request: since 0.8.1, when a search or feed comes back empty, the server sends one or two authenticated read-only GET probes (/memory/rooms and/or /memory/stats) so the empty answer can say what it did not cover. Since 0.16.0 a search or feed without domain that does return results also sends one, to /memory/rooms, so the answer can name the shared rooms it did not search. The probes carry your API key and nothing else, change no stored state, and are disclosed in the CHANGELOG.

Privacy Policy
Retention & deletion · correct a wrong or stale memory by writing a fresh one; deletion is an administrative operation on the REST API, not exposed through this MCP server
Contact · hello@mnemoverse.com

License

MIT © Mnemoverse

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Mnemoverse 怎么安装?

在客户端按下面的安装命令接入:claude mcp add mnemoverse -s user \ -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY \ -e MNEMOVERSE_API_URL=https://core.mnemoverse.com/api/v1 \ -- npx -y @mnemoverse/mcp-memory-server@latest。装完在客户端配置里引用同一个包或端点。

Mnemoverse 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Mnemoverse 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Mnemoverse 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Mnemoverse 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Cline;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Mnemoverse 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Mnemoverse 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Mnemoverse 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。