Hermes Atlas
Memory & knowledge

mnemosyne-hermes

juanmackie/mnemosyne-hermes

Hermes memory provider with local semantic search, plus a standalone SQLite store with CLI and MCP server

In short

mnemosyne-hermes is a memory provider distribution for Hermes Agent, plus a small standalone SQLite memory store with a CLI and an MCP server that works without Hermes.

What mnemosyne-hermes does

The repository ships two deliberately separate things. The main product is the Hermes memory provider under integrations/hermes-provider/, an engine-backed provider with the id mnemosyne that does keyword and vector search. The installer sets memory.provider to mnemosyne through hermes config set, installs the plugin into $HERMES_HOME/plugins/mnemosyne as a symlink or a verified copy, and checks that exactly one provider registers. It never creates or opens the memory database.

The second part is mnemosyne_lite, a standalone keyword store on SQLite with a mnemosyne-lite CLI and an MCP stdio server. It is not a Hermes provider and is useful for scripts and other MCP clients. No cloud API key is required for either half, and any optional LLM work in the engine uses the model Hermes is already configured with. The README includes a block you can hand to your agent to install the provider, verify it with hermes mnemosyne doctor and set up a daily, notify-only update check. The repository is not rand/mnemosyne.

Key features

  • Hermes memory provider with the id mnemosyne and keyword and vector search
  • Installer with a dry-run mode that prints the resolved venv, database path and plugin target
  • Symlink or verified-copy install with a PROVENANCE.json hash inventory
  • Standalone mnemosyne-lite SQLite store with a CLI
  • MCP stdio server for non-Hermes clients
  • Works without a cloud API key

When to use it

  • Giving a Hermes agent persistent memory that stays on your own machine
  • Letting an agent install and update the provider from a copy-paste prompt
  • Using a keyless SQLite memory store from scripts or MCP clients without Hermes

Who it is for: Hermes Agent users who want a local, keyless memory provider, and developers who want a small SQLite memory store with an MCP server.

How it fits with Hermes Agent

The provider is built for Hermes Agent and is activated through memory.provider; the lite store is a separate surface that does not need Hermes.

How to install mnemosyne-hermes

These commands are copied from the project's README. Check the repository for the latest steps before you run them.

git clone https://github.com/juanmackie/mnemosyne-hermes.git
cd mnemosyne-hermes
./install.sh --dry-run
./install.sh

Requirements: A Hermes install and its virtualenv, uv, and Python 3.11+ for the lite surface; no cloud API key

FAQ

What is mnemosyne-hermes?

mnemosyne-hermes is a Hermes Agent memory provider distribution. It ships an engine-backed provider named mnemosyne and a separate standalone SQLite keyword store with a CLI and MCP server.

Does mnemosyne-hermes work with Hermes Agent?

Yes. The provider installs into the Hermes plugins folder and is selected with memory.provider set to mnemosyne. The README says no particular Hermes version is required.

What do I need to run mnemosyne-hermes?

You need a Hermes install and its virtualenv, and uv. The lite surface also needs Python 3.11+. No cloud API key is needed.

Similar memory for Hermes Agent

All memory

Related guides: SOUL.md for Hermes Agent: what it is and how to write one · Run multiple Hermes agents with profiles