mnem-mcp
An MCP server that exposes a Mnemosyne store to an agent: its memory as tools and resources, so the agent records what it learns, and you can trace a wrong belief later.
pip install mnem-mcp # not published yet; build from the repo
mnem-mcp --store ./agent-memory # speaks MCP over stdio
Tools
remember, revise, remember_many, forget, recall, recall_at,
history, why, when_did, whats_new. With --tools all, also branch,
switch and merge (for a harness, not usually the model).
Every write tool is one commit. Provenance travels on remember as source /
step / observation.
Resources
mnem://memory, mnem://memory/{id}, mnem://log, mnem://commit/{id}, so a
client keeps the current memory in context without a tool call every turn.
How it binds
One store per server process, from --store or $MNEM_STORE. The server holds
no state between calls (the 2026-07-28 MCP transport is stateless); it opens the
store fresh each time. Concurrent writes serialise and retry; a persistent loser
returns the conflict code.
See ADR-0016.
1 maintainer
Metadata
1 maintainer
Release files for mnem-mcp 0.0.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 |
|---|---|---|---|---|
| mnem_mcp-0.0.1.tar.gz | 6.3 kB | Without provenance | Details for mnem_mcp-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mnem_mcp-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for mnem_mcp-0.0.1-py3-none-any.whl |
Total release size: 12.4 kB
Release files / mnem_mcp-0.0.1.tar.gz
| Download URL | mnem_mcp-0.0.1.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea74916008017ed1c7f6b5a0b2720641966168c763cf7429c8476907b3e7e673
|
|
BLAKE2b-256 checksum How to use checksums |
6ee42793f3c0b11de080da33a2561f0ad2f04c38b3c325d440864ba86b164d25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / mnem_mcp-0.0.1-py3-none-any.whl
| Download URL | mnem_mcp-0.0.1-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a14e9d29cde8c45f019cd2cd62b02d099e8ab42bcb04f5bb436098421fd3325
|
|
BLAKE2b-256 checksum How to use checksums |
c24815aee3b6f7dd22b7b367fd6d2fe8782e430ea7e28ba9741e3d7457073e98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for mnem-mcp 0.0.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.
