mnemosyne-mcp-server
Standalone Model Context Protocol (MCP) server for the Mnemosyne memory substrate. Exposes search, store, delete, context, list_projects, and get_profile tools to Claude Desktop, Cursor, and any MCP-compatible client.
Install
pip install mnemosyne-mcp-server
Configure
Set your API key:
export MNEMOSYNE_API_KEY="mn_..."
# Optional:
export MNEMOSYNE_BASE_URL="https://api.mnemosyne.geasslabs.xyz"
export MNEMOSYNE_DEFAULT_CONTAINER="default"
Run
stdio (default - for local clients like Claude Desktop)
mnemosyne-mcp
SSE / HTTP (for remote clients)
mnemosyne-mcp --transport sse --host 0.0.0.0 --port 8765
Use with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"mnemosyne": {
"command": "mnemosyne-mcp",
"env": {
"MNEMOSYNE_API_KEY": "mn_..."
}
}
}
}
Restart Claude Desktop. You'll see the Mnemosyne tools (memory, recall, context, list_projects, get_profile, delete) in the tool menu.
Use with Cursor
In .cursor/mcp.json:
{
"mcpServers": {
"mnemosyne": {
"command": "mnemosyne-mcp",
"env": {
"MNEMOSYNE_API_KEY": "mn_..."
}
}
}
}
Available tools
| Tool | Description |
|---|---|
memory |
Save a memory. |
recall |
Semantic search over memories. |
context |
Get a context bundle (profile + relevant memories). |
list_projects |
List all containers accessible to the API key. |
get_profile |
Get the learned profile for a container. |
delete |
Delete a memory by ID. |
For the full 29-tool surface (including dream, reflect, introspect, find_analogies, predict_outcome, what_if, etc.), use the in-process MCP server from the Mnemosyne monorepo.
License
MIT © Geass Labs
Metadata
Release files for mnemosyne-mcp-server 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 | Actions |
|---|---|---|---|---|
| mnemosyne_mcp_server-0.1.0.tar.gz | 5.8 kB | Without provenance | Details for mnemosyne_mcp_server-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mnemosyne_mcp_server-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for mnemosyne_mcp_server-0.1.0-py3-none-any.whl |
Total release size: 12.7 kB
Release files / mnemosyne_mcp_server-0.1.0.tar.gz
| Download URL | mnemosyne_mcp_server-0.1.0.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b70ac49111a062b26e3d50049d19a1adf18f39081fc37d6e4cc4f690becdee1
|
|
BLAKE2b-256 checksum How to use checksums |
74f4a911d59a73045c6271b4ad39c7fc2f0d0ecfe978cfc4a82ce29878feb5c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / mnemosyne_mcp_server-0.1.0-py3-none-any.whl
| Download URL | mnemosyne_mcp_server-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd54c4035487b42faf7b5194a374b60e0c65055bcb6bfae87bbe976578367541
|
|
BLAKE2b-256 checksum How to use checksums |
50b8c02beb5d223a1c862f5ba345fccad505b40152571288db5f2a430842dae8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for mnemosyne-mcp-server 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.