Hermes

HydraDB is a native Hermes Agent memory provider: relevant context is recalled before each turn and completed turns are persisted automatically. This is the proper, native way to make HydraDB Hermes’ long-term memory (alongside providers like supermemory, retaindb, and ham). It uses the HydraDB public API only (recall + knowledge ingest); no HydraDB SDK is required.

Quick Start

Install the provider

Catalog (recommended)
Directory (drop-in)
pip (entry point)

HydraDB is a first-party entry in the curated Hermes plugin catalog:

hermes plugins install hydradb
hermes memory setup hydradb

Clone the repo and copy the hydradb_hermes/ folder (it contains __init__.py and plugin.yaml) into your Hermes memory plugins directory:

git clone https://github.com/hydra-db/hydradb-hermes-plugin.git
mkdir -p ~/.hermes/plugins/memory/hydradb/
cp -r hydradb-hermes-plugin/hydradb_hermes/. ~/.hermes/plugins/memory/hydradb/

pip install hydradb-hermes

Registered via the hermes_agent.memory_providers entry point.

Requires Python 3.10+ and a Hermes Agent install.

Get credentials

Create an API key from the HydraDB dashboard
Create or copy your database ID from the HydraDB dashboard

Set environment variables

export HYDRADB_API_KEY="your-api-key"
export HYDRADB_DATABASE="your-database"

Enable it in config.yaml

Memory providers are single-select:

memory:
  provider: hydradb

How It Works

The integration implements Hermes’ MemoryProvider contract:

Method	Role	HydraDB
`prefetch(query, *, session_id)`	Auto-recall: context injected before the API call	Hybrid `POST /query` (prefers the server-built `llm_prompt`)
`sync_turn(user, assistant, ...)`	Persist the completed turn (non-blocking, off-thread)	`POST /context/ingest`
`is_available()`	Provider availability	`bool(HYDRADB_API_KEY)`
`get_config_schema()` / `save_config()`	Setup wizard (API key, tenant)
`name`	Provider name	`"hydradb"`

Auto-recall: Before each turn, Hermes calls prefetch, which queries HydraDB and returns graph-enriched context to inject into the request.
Auto-retain: After each turn, sync_turn persists the user/assistant exchange off-thread so the model is never blocked on a write.

MCP Alternative

For pull-style recall (agent-invoked tools) instead of automatic memory, point Hermes at the HydraDB MCP server. The memory provider already gives automatic recall and retain, so MCP is optional.

Source & Show Support

If this HydraDB provider makes Hermes smarter, please star the open-source repo that powers it.

hydradb-hermes-plugin

Star on GitHub if you found it useful.

Get Started

Usage

Concepts

Plugins

For Agents

Quick Start

How It Works

MCP Alternative

Source & Show Support

hydradb-hermes-plugin

​Quick Start

​How It Works

​MCP Alternative

​Source & Show Support

hydradb-hermes-plugin

Quick Start

How It Works

MCP Alternative

Source & Show Support