Spomory
Explainable graph-retrieval memory engine with an RL-trained management policy.
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.lyf-wxy/spomory
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
English | 中文
Spomory gives Claude Desktop, Cursor, and Codex CLI a memory that persists across sessions — and is shared between all three. Tell one of them something once (a project detail, a preference, a fact about yourself) and any of them can recall it later, without you repeating yourself.
It runs as an MCP server, either locally on your own machine (free, nothing leaves your computer) or as a hosted cloud service (free signup, memory follows you across devices). The rest of this README covers the local path; for the cloud path see spomory.yliuai.com/get-started/remote.
Curious what it looks like before installing anything? There's a no-signup demo at spomory.yliuai.com — paste in some text, see the entities and relations it extracts.
Get started
Requires Python 3.11+.
1. Install
pip install "spomory[llm,embedding,mcp]"
2. Give it an LLM. Spomory uses an LLM to turn what you tell it into structured facts. Any OpenAI-compatible API works — OpenAI, DeepSeek, Qwen, etc.:
export LLM_API_KEY=sk-...
export LLM_BASE_URL=https://api.deepseek.com # optional, defaults to OpenAI
export LLM_MODEL=deepseek-chat # optional, defaults to gpt-4o-mini
3. Connect it to your client. Claude Desktop, Cursor, and Codex CLI
each need a few lines added to a config file, pointing at the
spomory-mcp command. The exact steps, a config file example for each
client, and a real gotcha we hit (macOS blocking a venv that lives under
~/Documents) are in
docs/mcp_quickstart.en.md.
The one thing that trips people up: the config needs the absolute path to
spomory-mcp(runwhich spomory-mcpto find it) — the client doesn't necessarily launch it with your shell'sPATHset.
That's it. Data lives locally in ~/.memory-core/ by default (override
with MEMORY_CORE_DATA_DIR). A Dockerfile is also
included, for MCP directories/hosts that deploy from a container image
instead.
What it can do
Once connected, six tools become available inside the client:
| Tool | What it does |
|---|---|
add_memory |
Remembers something you tell it |
search_memory |
Recalls whatever's relevant to a question |
forget_memory |
Deletes the one thing that best matches what you asked to forget |
forget_all_memory |
Wipes the entire memory graph in one call |
get_graph |
Shows the memory graph around something, for inspection |
export_memory |
Exports everything you've stored, as JSON — your data, portable |
All six are verified working end-to-end against real Claude Desktop,
Cursor, and Codex CLI sessions, both local and remote — see
docs/mcp_quickstart.en.md for what
"verified" means for each client.
How it works, for the curious
You don't need any of this to use Spomory — it's here for people who want to know what's actually happening underneath.
From the project's README.