Summary
A memory the model queries in prose, instead of a notes file it has to grep.
The whole surface is two calls, which is the point: read takes a search term or 'ALL', write takes content and a mode. There is no edit path in the tool list — sTool switches between NEW and DELETE only — so revising a memory means deleting the old entry and writing a fresh one, and the id of what you are deleting comes from a read first.
What it is
A two-tool memory store: read searches it, write changes it, and the entries themselves are free-form.
What you get
- Semantic retrieval across stored memories, with synonyms, fuzzy matching and context understanding rather than literal matching
- Everything at once through the search term 'ALL', or just the matching entries for anything else
- Additions and deletions through one write tool, switched between NEW and DELETE by sTool
- Entries in whatever shape suits — structured notes, preferences, facts or passing thoughts
Requirements
No account and no key; the store is the server's own. Deletions are addressed by id, so a memory has to be found through read before it can be removed.
Setup effort
One command — npx @frgmt/inked