CLI reference
The fluree memory subcommands, alphabetically-ish.
| Command | Purpose |
|---|---|
init | Create the memory store and optionally configure MCP for detected AI tools |
add | Store a new memory |
recall | Search and rank relevant memories |
update | Update an existing memory in place |
forget | Retract a memory permanently |
status | Summary of the store (totals, tags, kinds) |
export / import | Round-trip memories as JSON |
mcp-install | Install MCP config for an IDE |
Several subcommands take a --format flag (text for humans, json for scripts, and context on recall for XML intended for LLM injection). The default is always text.
The common options
A few flags show up across many subcommands:
| Flag | Default | Where |
|---|---|---|
--scope <repo|user> | repo | add; filter on recall |
--tags <t1,t2> | none | add, update; filter on recall |
--kind <kind> | fact on add | add; filter on recall |
--format <text|json> | text | add, update |
--format <text|json|context> | text | recall (XML context is for LLM injection) |
See What is a memory? for the kind taxonomy.
Environment
| Variable | Effect |
|---|---|
FLUREE_HOME | When set, the CLI and MCP server use this path as the unified Fluree directory. If unset, both walk up from CWD looking for an existing .fluree/; if none is found, they fall back to a platform-global config/data directory. |
Set FLUREE_HOME=<repo>/.fluree if you need to force repo-scoped operation from a shell that starts elsewhere. Among the IDE integrations, only the Cursor MCP config sets this automatically via ${workspaceFolder}; the others rely on the walk-up behavior from spawn CWD.