Expanding full CLI tools alongside MCP integrations
Expanded first-class CLI tooling so teams can run memory workflows directly in scripts and terminals, not only via MCP clients.
Expanding CLI tools alongside MCP integrations
MCP is a strong interface, but teams operate across multiple surfaces.
The gap identified
Some workflows needed direct CLI execution without requiring an MCP host in every step, especially in shell scripts and CI.
If teams cannot run memory operations in automation, adoption stalls.
What shipped
- Broader first-class CLI command surface.
- Better parity between CLI and MCP outcomes.
- Easier scripting for routine memory operations.
The outcome
Portability improved in environments where terminal and automation workflows are primary.
A common support question, "how to run this outside chat," decreased after this release.
Practical next steps
- Add CLI examples for the top three automation workflows in your team.
- Validate output parity between CLI and MCP for key operations.
- Include CLI-based smoke checks in CI for memory-critical flows.