MCP Memory
A Model Context Protocol (MCP) server implementing memory solutions for data-rich applications with efficient knowledge graph capabilities.
Overview
This MCP server implements a memory solution for data-rich applications that involve searching information from many sources including uploaded files. It uses HippoRAG internally to manage memory through an efficient knowledge graph.
Features
- Session-based Memory: Create and manage memory for specific chat sessions
- Efficient Knowledge Graph: Uses HippoRAG for advanced memory management
- Multiple Transport Support: Works with both stdio and SSE transports
- Search Capabilities: Search information from various sources including uploaded files
Installation
Install from PyPI:
pip install mcp-mem
Or install from source:
git clone https://github.com/ddkang1/mcp-mem.git
cd mcp-mem
pip install -e .
Usage
You can run the MCP server directly:
mcp-mem
By default, it uses stdio transport. To use SSE transport:
mcp-mem --sse
You can also specify host and port for SSE transport:
mcp-mem --sse --host 127.0.0.1 --port 3001
Configuration
To use this tool with Claude in Windsurf, add the following configuration to your MCP config file:
"memory": {
"command": "/path/to/mcp-mem",
"args": [],
"type": "stdio",
"pollingInterval": 30000,
"startupTimeout": 30000,
"restartOnFailure": true
}
The command field should point to the directory where you installed the python package using pip.
Available Tools
The MCP server provides the following tools:
- create_memory: Create a new memory for a given chat session
- store_memory: Add memory to a specific session
- retrieve_memory: Retrieve memory from a specific session
Development
Installation for Development
git clone https://github.com/ddkang1/mcp-mem.git
cd mcp-mem
pip install -e ".[dev]"
Running Tests
pytest
Code Style
This project uses Black for formatting, isort for import sorting, and flake8 for linting:
black src tests
isort src tests
flake8 src tests
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Metadata
Release files for mcp-mem 0.1.0
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 | |
|---|---|---|---|---|
| mcp_mem-0.1.0.tar.gz | 16.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_mem-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.4 kB
Release files / mcp_mem-0.1.0.tar.gz
| Download URL | mcp_mem-0.1.0.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5128d80c196578bff6d68441cabac93d8e477605656e40f65e59ed94e133a47f
|
|
BLAKE2b-256 checksum How to use checksums |
1873fcfd3dc654673b5241a508c4a120cc3839c459b8dbb671e444eb6b378d14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / mcp_mem-0.1.0-py3-none-any.whl
| Download URL | mcp_mem-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52109a2f4199ece5db7e62ecdb037c21a0694fc801a24e8d753f71a740ae8d46
|
|
BLAKE2b-256 checksum How to use checksums |
e12f73eb5c5b21af386d0d1304dcebe8fc8224f91ab9f41ef4f77a628fa8d597
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for mcp-mem 0.1.0
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.