Folders

The hierarchy notes live in, and the context it carries.

7 tools — 4 read, 3 write.

Tool		What it does
folders_create	write	Create a context folder — an instruction-fronted container that groups related notes.
folders_delete	write	Delete a context folder.
folders_get	read	Open a folder: returns its instruction header (how to use it), the child folders it routes to, and the notes filed in it (titles only — pull note content lazily with notes_get).
folders_list	read	List context folders.
folders_root	read	Open the organization's root context folder — the company grounding entry-point.
folders_update	write	Update a folder's name and/or its instruction header.
load_context	read	Open a context folder and load its instruction header plus a lazy manifest of what it routes to — child folders and the notes filed in it (id, title, description only).

Calling these

Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.

See How the API works for auth, errors and the shared envelope.