Storage Backends

By default, the server uses a SQLite database to store memories locally. Eidetic supports multiple storage layers through the --storage-backend CLI flag or the EIDETIC_STORAGE_BACKEND environment variable.

Available Backends

Memwal

Recommended when you want Eidetic memories to be searchable through Memwal while preserving Eidetic’s MCP behavior for exact reads, updates, deletes, projects, sessions, prompts, and relations.

Code


eidetic --storage-backend memwal serve

Memwal writes store a stable Eidetic payload on-chain via Memwal and also write a local SQLite index. Search first attempts Memwal recall, then falls back to the local SQLite index for exact matching and compatibility.

SQLite

SQLite is the default backend and requires no external services. It stores all projects, observations, sessions, prompts, relations, and search index data locally.

Code


eidetic --storage-backend sqlite serve

Choose a custom database directory:

Code

eidetic --storage-backend sqlite --storage-path ~/.local/share/eidetic-mcp/storage serve

File

The file backend stores JSON documents sequentially on disk.

Code


eidetic --storage-backend file serve