Update a note
brain_node_updateUpdate an existing note in place to avoid near-duplicates: append text or replace the full body, and change tags or importance. Checks the note version and retries on concurrent edits.
Instructions
Update an existing note in place instead of creating a near-duplicate. mode "append" (default) adds your text to the end and keeps everything already there; mode "replace" overwrites the whole body, so only use it when you have the full corrected text (read it with brain_node_get first). Tags and importance, if given, replace the existing values. Safe against concurrent edits: it checks the note version and retries once if another writer changed it in between. Returns { success: true, id, mode } (mode is omitted when only tags or importance changed). Errors: "not found" for an unknown id, "Nothing to update" if you pass only an id, and a conflict error if two other writers keep racing; in that case read the note again and retry. No credentials are needed from you: if the server was started with BRAIN_KEY, this MCP server sends it automatically.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Note id exactly as returned by brain_search, brain_recall or brain_remember, e.g. "agents/my-project/Decision - Use SQLite". | |
| mode | No | "append" (default) keeps the existing text and adds yours at the end. "replace" overwrites the whole body: read the note first with brain_node_get. | append |
| tags | No | The note's new complete tag list; it replaces the old tags rather than adding to them. | |
| content | No | In append mode, the text to add after the existing body. In replace mode, the complete new body (it overwrites everything, so include whatever you want to keep). Omit to change only tags or importance. | |
| importance | No | New importance, 1 to 10 (see brain_remember). |