MCP server for Mnemosyne: an AI agent's memory as tools and resources.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mnem-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mnem-mcp An [MCP](https://modelcontextprotocol.io) server that exposes a [Mnemosyne](https://github.com/Nabzx/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. ```bash 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](../../docs/adr/0016-mcp-tools-and-the-adapter-contract.md).
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.