Configuration

Eidetic can be configured heavily through environment variables and command-line flags. This is especially useful when integrating the server into existing agents via their mcp.json configuration blocks.

Global Settings

FlagEnvironment VariableDescription
--storage-backendEIDETIC_STORAGE_BACKENDSpecifies the storage engine (sqlite, memwal, file).
--storage-pathEIDETIC_STORAGE_PATHThe local directory to store SQLite databases or File JSON documents.

Memwal Backend Configuration

When using the memwal storage backend, you can fine-tune how Eidetic communicates with the Sui network and the Memwal relayer.

FlagEnvironment VariableDescription
--memwal-account-idEIDETIC_MEMWAL_ACCOUNT_IDSpecific account ID to use.
--memwal-registry-idEIDETIC_MEMWAL_REGISTRY_IDOverride the default Memwal Registry ID.
--memwal-server-urlEIDETIC_MEMWAL_SERVER_URLCustom RPC endpoint for the Sui network.
--memwal-relayer-config-urlEIDETIC_MEMWAL_RELAYER_CONFIG_URLOverride relayer discovery URL.
--memwal-namespaceEIDETIC_MEMWAL_NAMESPACEMemory namespace (defaults to eidetic).
--memwal-delegate-labelEIDETIC_MEMWAL_DELEGATE_LABELDelegate label (defaults to eidetic-mcp).
--sui-config-dirEIDETIC_SUI_CONFIG_DIRDirectory containing your Sui wallet configuration (defaults to ~/.sui/sui_config).

Sui Account Selection for Memwal

Account selection is handled natively by Eidetic’s authentication layer. On startup, Eidetic reads ~/.sui/sui_config/client.yaml, evaluates aliases, and checks sui.keystore. It defaults to the active address, ensuring that memory management happens locally without exposing private keys over the network.