Skip to main content
Glama
CROW: LLM Wiki

CROW: LLM Wiki

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OKF_BUNDLENoFolder of the Markdown wiki. Optional: by default a wiki in the user's home folder, made empty on first start.
OKF_MCP_MODELSNoWhose 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 recall before 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 remember when 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_file with a document's path when the user asks you to add, import or file it ("add this PDF…", "aggiungi questo file…"); sync_folder for a whole folder.

  • Call search to find notes by their words with no answer written (fast, no model), when you will read them yourself.

  • Call read_note to read a cited note in full.

  • To reorganize when the user asks ("move…", "sposta…", "rinomina…", "cancella…"): folders lists the folders, then move_note, describe_folder, rename_area, merge_areas, delete_note. Delete or merge only what the user asked for; when unsure, ask first.

  • When recall or remember returns requests instead of a result, the memory works with your models: follow its how. Never store secrets: keys, passwords, tokens.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 remember; for matching notes with no answer written, search. A model writes the answer. Returns {answer, notes, titles}: notes are the cited paths, to read in full with read_note. With your models, it returns a job with requests instead: answer them with reply.

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 remember_file. A classifier picks the folder and whether to merge into the note on the same subject; a model writes the note and links related ones. Returns {action: created | merged | unchanged, note, folder, related}. Adds or merges, never deletes. Never store secrets. With your models, it returns a job with requests instead: answer them with reply.

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 move_note or delete_note. Destructive and slow: every note, raw copy and archived version is deleted before the documents are filed again; the folders and their descriptions stay and none is opened. Without confirm=true it refuses and changes nothing. A rebuild that stops can be run again. Returns counts of the documents filed and the errors.

replyA

Send your answers to the memory's pending requests; returns its next requests or the final result.

Call it only after recall, remember, remember_file, sync_folder or rebuild returned a job: the memory then works with your models. Answer each request as its how says, then pass the job and {request id: your reply}. With status "waiting", call it with the job and {} until the work ends. Each call waits up to 50 seconds and returns new requests, or {status: "done", ...} with the result the first tool would have given. A job's result is kept 10 minutes after it ends.

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_note; to get an answer to a question, use recall. Fast: no model is called. Returns up to k notes, each with its path, title, summary and rank.

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 recall cited or search found, before quoting details its summary lacks; for an answer drawn from several notes, use recall. No model call. An unknown path returns an error naming it.

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_area. New notes are routed by the description. Moves no note. Returns the folder and its description; refused with an error when the memory already has as many top-level folders as its limit.

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 create_area. Nothing moves until confirm_area settles the proposal with the user's yes or no. Returns the proposal with its id, name, description and notes.

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_area; to make a new one, use propose_area. Empty when none is open.

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 propose_area or proposals, never to answer for the user. A yes returns the proposal and the notes moved, whose links follow them; it is refused with an error when the memory already has as many top-level folders as its limit. A no moves nothing and closes the proposal.

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_note, describe_folder, rename_area or merge_areas, or to tell the user which areas exist; to find notes by their words, use search. No model call.

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 merge_areas. The note's text does not change and no model is called. Returns the note's new path; an unknown note returns an error.

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_area; to move notes already filed, move_note. Notes already filed stay where they are: only new notes follow the new line. Returns the folder and its new description.

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 describe_folder; to fold it into another, merge_areas. Top-level folders only. Returns the folder's new name and its description.

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 move_note. Destructive: the source folder and its description are deleted, its notes are kept in the target. Without confirm=true it refuses and changes nothing. Returns the target folder and its description.

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 move_note. Cannot be undone. Without confirm=true it refuses and changes nothing. Returns the note deleted; an unknown path returns an error.

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_folder, for something said in chat remember. Its text is filed as remember files a text, a spreadsheet one note per sheet, and the file's path is kept as the source. Returns {action, note, folder, related}. Adds or merges, never deletes. An unknown path returns an error. With your models, it returns a job with requests instead: answer them with reply.

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 remember_file. The first call files every readable document; a later call files only the new and changed ones, with no model call for the rest. A file removed from the folder is marked as removed, and its notes stay. Returns counts (created, merged, unchanged, removed, skipped) and the errors. With your models, it returns a job with requests instead: answer them with reply.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 18 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityActive
ResponsivenessLimited data