MCP tools
The tools a connected agent uses to read and update your vault.
Connect your agent under Connect agents in the app – via sign-in (Claude, ChatGPT) or an access key (Claude Code, Cursor).
Reading
Requires the read permission.
| Tool | Purpose |
|---|---|
vault_overview | Entry point: structure, rooms and the rules from 9_System/ |
search_notes | Full-text search with snippets, including German word forms |
read_note | One note by path or title, with version number |
list_notes | Contents of a folder |
get_backlinks | Which notes link to this note |
Responses always include path, title, version and room, so the agent can continue precisely.
Writing
Requires the read and write permission. Every change needs a short summary (change_summary) that shows up in the history.
| Tool | Purpose |
|---|---|
create_note | New note with path and content |
append_to_note | Append text at the end or under a heading |
update_section | Replace the content under a heading |
replace_note | Replace a whole note – only with a matching expected_version |
append_to_note and update_section are the normal case: they change only what they should, and they work even while you are typing at the same time.
Addressing sections
A section runs from its heading to the next heading of the same or a higher level. You address it by the heading text:
| Input | Matches |
|---|---|
Timeline | the heading "Timeline", at any level |
## Timeline | only a level 2 heading |
Projects > Goals | "Goals" below "Projects" |
If a heading appears more than once, the agent gets an error listing all candidates as paths instead of a guess.
Conflicts
If a note has changed since it was read, replace_note fails and names the expected and the current version. The agent reads the note again and reapplies its change.
What doesn't exist
- Deleting: only in the app, never via MCP.
- Mass changes: If a connection writes an unusual amount per minute, it gets slowed down.