Zum Inhalt springen

Capabilities

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Read tools require library:read; write tools require library:write. Tools act only on the connected account’s Library. Paginated read results use opaque, short-lived cursors.

Search current Pages with a query of up to 512 characters. Results contain Page IDs, titles, folder paths, tags, summaries, and bounded excerpts. Semantic retrieval is enabled by default and uses the shared per-account MCP call limits.

Read the current Page body by Page ID. Long bodies are returned in 16 KiB chunks; pass next_cursor back to continue. The cursor is bound to the user, grant, and Page request.

Browse Page or folder metadata. Use kind: "pages" or kind: "folders", optionally with a short query.

Follow explicit outgoing links, backlinks, or both for one Page. The result contains linked Page metadata and the relationship direction.

Retrieve a Page’s current structured V1 PageDocument JSON for editing. Unlike get_page, which returns readable body text in chunks, this tool returns serialized JSON in json_chunk values; concatenate chunks in cursor order and parse them before editing. Page Documents can exceed the MCP response-size limit, so larger documents require multiple calls.

  • create_page: create a Page in the Library with V1 PageDocument content.
  • update_page: update a Page, including its full V1 PageDocument content. Send the Page’s updated_at as expected_updated_at to prevent overwriting a newer edit.
  • delete_page: delete a Page. Requires expected_updated_at.
  • create_folder: create a folder.
  • update_folder: rename a folder using its updated_at as expected_updated_at.
  • delete_folder: delete a folder and all its descendant folders and Pages. Requires the folder’s expected_updated_at and confirm_cascade: true. This revision guards changes to the folder itself, not new or edited Pages inside it; check the target and its contents immediately before deletion.

For updates and deletes, copy the item’s updated_at from get_page, get_page_document, or list_library (for folders) into expected_updated_at. If that item has changed since you read it, the write fails instead of applying to an outdated version.

Page content for writes is structured V1 PageDocument JSON. A simple document looks like this:

{"type":"doc","content":[{"type":"paragraph","content":[{"type":"text","text":"Hello, Library."}]}]}

MCP does not expose Chute Notes, historical Page snapshots, raw database fields, or Ask conversations. Write-capable clients can change or delete Library content without a separate Zenodot approval step for each tool call.