Super-Memory
A semantic memory storage and retrieval MCP (Model Context Protocol) server using LanceDB and sentence transformers.
What is Super-Memory?
Super-Memory gives your AI agents long-term memory across sessions. It stores and retrieves information using semantic embeddings, so agents can recall relevant context from previous conversations, files, and web pages.
Features
- Semantic search - Query memories by meaning, not just keywords
- File memory - Read and store local file contents
- Web memory - Fetch and store web page contents
- Boomerang context - Special support for Boomerang Protocol session state
- Local storage - All data stays on your machine in
./memory_data
Tools
| Tool | Description |
|---|---|
save_to_memory |
Store text with optional metadata |
save_file_memory |
Read a file and store its content |
save_web_memory |
Fetch a URL and store its content |
query_memory |
Semantic search across all memories |
list_sources |
List all stored sources |
recall_source |
Retrieve exact source by path |
save_boomerang_context |
Save Boomerang session context |
get_boomerang_context |
Retrieve Boomerang session context |
Installation
Using uv (recommended)
uv tool install super-memory-mcp
Using pip
pip install super-memory-mcp
Manual / Development
git clone https://github.com/Veedubin/Super-Memory.git
cd Super-Memory
uv sync
uv run super-memory-mcp
OpenCode Configuration
Add to your .opencode/opencode.json:
{
"mcp": {
"super-memory-mcp": {
"type": "local",
"command": ["uv", "run", "super-memory-mcp"],
"enabled": true
}
}
}
Or if installed with uv tool:
{
"mcp": {
"super-memory-mcp": {
"type": "local",
"command": ["super-memory-mcp"],
"enabled": true
}
}
}
Requirements
- Python >= 3.13
- CUDA (optional but recommended) - falls back to CPU automatically
- ~500MB disk space for the embedding model (downloaded on first run)
First Run
On first startup, Super-Memory will download the sentence-transformers/all-MiniLM-L6-v2 sentence transformer model. This may take a few minutes depending on your internet connection.
Data Storage
Memories are stored locally in a ./memory_data directory relative to where you run the command. Each project should ideally run Super-Memory from its own directory to keep project-specific memories separate.
License
MIT License - see LICENSE
Metadata
Release files for super-memory-mcp 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| super_memory_mcp-0.5.1.tar.gz | 350.2 kB | Without provenance | Details for super_memory_mcp-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| super_memory_mcp-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for super_memory_mcp-0.5.1-py3-none-any.whl |
Total release size: 366.5 kB
Release files / super_memory_mcp-0.5.1.tar.gz
| Download URL | super_memory_mcp-0.5.1.tar.gz |
|---|---|
| Size | 350.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df6bfdb4d5d661ac5ee0eb5003c0160611bf66250157f586fc405ec85c087601
|
|
BLAKE2b-256 checksum How to use checksums |
45854f9f4f8d352220907115755aee266658e7b2f4439e52cf2a926fb3912a96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / super_memory_mcp-0.5.1-py3-none-any.whl
| Download URL | super_memory_mcp-0.5.1-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8ce89a2ab802300e8f368a988e7b6b2d5a3bca67331e180658159be9af13fa0
|
|
BLAKE2b-256 checksum How to use checksums |
622d607764fdcd009767d8c0f11b5b04468969b4c5d977e27afc44dea61ab69b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for super-memory-mcp 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.