read
Search and retrieve memories using powerful semantic search. Use 'ALL' to get all memories, or search terms for intelligent matching including synonyms, fuzzy matching, and context understanding.
LABSCO 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
USE CASES
01
Carrying a preference across sessions instead of restating it
Write the fact once in whatever form suits it, and let later sessions find it by meaning rather than by the words you happened to use.
02
Clearing out a memory that has gone stale
Search for the entry to get its id, then delete it — a correction is a removal followed by a fresh write, since there is no edit mode.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
write
Add new memories or delete existing ones. Use sTool="NEW" to add, sTool="DELETE" to remove. Memories can be any format - structured notes, preferences, facts, or simple thoughts.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"inked": {
"command": "npx",
"args": [
"@frgmt/inked"
]
}
}
}npx
TERMINAL
npx @frgmt/inked
