CROW: LLM Wiki
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OKF_BUNDLE | No | Folder of the Markdown wiki. Optional: by default a wiki in the user's home folder, made empty on first start. | |
| OKF_MCP_MODELS | No | Whose models do the memory's work: client (the MCP client's own models, no key needed), hybrid, or wiki (the wiki's own writer and classifier, which need their API keys). | client |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Your long-term memory: a wiki of Markdown notes on this computer, which already holds the user's documents. A typed classifier decides where each note goes and a model writes it (CROW). The user speaks to you in plain words, in any language, and never names these tools: use them on your own.
Call
recallbefore you answer about the user's work, projects, people, documents, decisions or preferences, and whenever they mention something from before ("what did we decide about…", "ti ricordi…", "cosa sappiamo di…"). Cite the notes it returns as [path.md].Call
rememberwhen the user asks you to keep something ("remember that…", "ricorda che…", "segnati…", "annota…", "from now on…", "d'ora in poi…"), and on your own when something durable is settled: a decision and why, a fix that worked, a preference, a fact about a project or a person. One topic per call, written to make sense without this conversation, in the user's language.Call
remember_filewith a document's path when the user asks you to add, import or file it ("add this PDF…", "aggiungi questo file…");sync_folderfor a whole folder.Call
searchto find notes by their words with no answer written (fast, no model), when you will read them yourself.Call
read_noteto read a cited note in full.To reorganize when the user asks ("move…", "sposta…", "rinomina…", "cancella…"):
folderslists the folders, thenmove_note,describe_folder,rename_area,merge_areas,delete_note. Delete or merge only what the user asked for; when unsure, ask first.When
recallorrememberreturns requests instead of a result, the memory works with your models: follow itshow. Never store secrets: keys, passwords, tokens.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recallA | Answer a question from the user's long-term memory, citing the notes the answer comes from. Call it before you answer about the user's work, documents, people, decisions or anything from before, in any language. Not to save something: use |
| rememberA | Save a fact, decision or text in the long-term memory, in the folder and note where it belongs. Call it when the user asks you to remember or note something, and on your own when something durable is settled (a decision and why, a preference, a fact about a project or a person): one topic per call, self-contained. For a document on disk, use |
| rebuildA | Delete every note and file all the documents again from the memory's raw copies, into the same folders. Call it only when the user explicitly asks to rebuild the whole memory; to fix one note use |
| replyA | Send your answers to the memory's pending requests; returns its next requests or the final result. Call it only after |
| searchA | Find the notes whose words best match a query, best first, with no answer written. Use it for a name, a code, a quoted phrase or keywords when you will read the notes yourself with |
| read_noteA | Return the full text of one note: its title, its summary and its Markdown body. Call it to read in full a note that |
| create_areaA | Open a new, empty top-level folder (an area) with a one-line description of what belongs in it. Call it only when the user asks for a new area; the memory never opens one on its own. To gather existing notes into a new area, use |
| propose_areaA | Propose a new top-level folder that gathers existing notes, for the user to approve. Call it when the user describes an area for notes already in the memory; for an empty one, use |
| proposalsA | List the open proposals of new top-level folders, each with its id, name, description and notes. Call it to put the pending proposals to the user as a yes or a no, then settle each with |
| confirm_areaA | Settle a proposal of a top-level folder with the user's answer: yes opens it and moves its notes, no dismisses it. Call it only with the user's explicit answer to a proposal from |
| foldersA | List every folder of the memory with its one-line description and how many notes it holds directly. Call it to see how the memory is organized before |
| move_noteA | Move one note into another folder; the links to and from it follow. Call it when the user asks to move a note; to move every note of a top-level folder, use |
| describe_folderA | Change a folder's one-line description, the line new notes are routed by. Call it when the user redefines what a folder is for; to rename it, use |
| rename_areaA | Rename a top-level folder; its notes and the links to them follow. Call it when the user asks to rename an area. To change what it is for, use |
| merge_areasA | Move every note of one top-level folder into another, then delete the emptied folder. Call it only when the user asked to merge two areas; for one note, use |
| delete_noteA | Delete one note for good; the links to it are removed from the other notes. Call it only when the user asked to delete that note; to put it elsewhere, use |
| remember_fileA | File a document from this computer's disk: text, Markdown, PDF, Word, PowerPoint, Excel or OpenDocument. Call it when the user asks to add, import or file a file; for a whole folder use |
| sync_folderA | File every document of a folder on this computer and keep the memory in step with it. Call it when the user asks to import or update a whole folder; for one file use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct operation in the memory lifecycle: recall answers, search finds, read_note reads, and the area proposal tools (proposals, propose_area, confirm_area, create_area) are separate steps with explicit cross-references. No two tools appear to do the same job.
All names use lowercase snake_case, and most follow verb_noun (create_area, move_note, sync_folder, remember_file). The plural-noun list tools (proposals, folders) and bare verbs (recall, search) are minor deviations but remain readable and predictable.
18 tools for a full memory system with notes, areas, import, jobs, and rebuild is slightly above the ideal 3–15 range. However, each tool covers a distinct operation, so the surface feels rich rather than redundant.
The set covers note create/read/delete/move, area create/list/rename/describe/merge, file and folder import, and rebuild. Notable gaps remain: no explicit note update/edit tool and no way to list notes within a folder; deleting an empty area is only possible through a merge workaround.