MCP

Return changed or missing sources and the exact claim ids that need review. Read-only.

Nothing here is permanently deleted.

Responder identity is a name only when the reader was signed in.

Each entry says what it is for, what fields it holds, and how a folder of them is laid out. Types under `editable` were designed from a blueprint and can be changed with update_item_type. For a source-less workspace look, request its full definition with template_id, then change that validated definition. A built-in must first be copied with remix_item_type. `needsMigration` and `unreadable` retain their old rendering and cannot be edited here. Call this first whenever someone wants a kind of item to be different. Supply template_id to inspect one complete render definition before editing it.

Only item editors can read removed text. Returns up to 50 records, newest first.

Read-only.

Combines word matching with meaning-based matching when the workspace has embeddings, and says which found each result. Every result carries the item id, folder, publisher, and original link to cite. Read-only.

Returns the chosen command, its arguments, and why. Reads run immediately. A write runs only when execute is true and this connection may call that command; otherwise the mapped call is returned for the caller to make. There is no new capability here: every command it can pick is one the connection could already call directly, with the same permissions, proposals, and audit.

The copy keeps its fields, item layout, folder layout, theme, and example. It is a separate type with a new id; the source and items using it are unchanged. Use this before modifying a built-in. Then inspect the copy with list_document_templates(template_id) and change it with update_item_type.

The blueprint defines the fields, the item page, the folder layout, example content, and safe theme tokens together. Use this when someone asks for a new kind of thing, such as a Medium-like blog, a Notion-like task board, or Apple Notes-like notes. If folder_path is supplied, the new type becomes that folder's default. Existing items change only when apply_to_existing is explicitly true. Use the document's existing title, body and assets before adding custom fields. Notes and blog articles can use fields: [] with showBody: true. Do not add Area, Description or other metadata merely to fill a quota. Add fields only when the requested workflow needs them. {"name":"Blog","styleReference":"Medium","fields":[],"item":{"shape":"article","showBody":true,"showMetadata":false},"collection":{"layout":"list"}} A board needs a single-select enum to group by, and a calendar or heatmap needs a date field to place items on: declare that field, or choose a layout the available content supports. Respect the requested reading and editing experience.

For blueprint-authored types, send the whole edited blueprint from list_document_templates. For an assembled or remixed workspace type, request list_document_templates with its template_id and send the whole edited definition. Only one of blueprint or definition is allowed. Definitions are validated render data, never HTML, CSS, JavaScript, or component names. Send base_version exactly as reported so an edit made against a stale copy is refused. Keep the definition id and version unchanged in the request; the save creates a new immutable version. The old version is kept and the items already using it keep rendering as they were. Use save_scope to name the selected folder or the exact listed usages, or to save only a version. Calls without save_scope save only a version unless apply is explicitly true. Only items pinned to that exact base reference are restyled. Existing field ids, storage kinds and enum values must stay compatible; change enum labels to rename options. Built-in types cannot be changed in place; first make a copy with remix_item_type. A type with an unreadable or outdated source needs manual recovery before editing.

The look then appears in the look pickers and can be applied to other items or given to a folder with set_folder_template. This replaced an operations-based authoring API: shape a document the ordinary way, with update_item and the item's own theme, then save what you made. It never changes the item.

Existing items retain their pinned types. Set apply_to_existing true only when the user explicitly asks to migrate existing items.

Omit template_version to use the look's current version, which is almost always what you want.

Overlapping changes return a comparison without changing the document. Does not alter human undo history or visibility.

For quick capture, pass capture alone: text becomes a private Note and a URL becomes a Bookmark, with a receipt in the result. For precise creation, pass fields or a full markdown file and choose a folder. New items are never published or pinned. Automated clients should pass a stable idempotency_key so retries cannot create duplicates.

A full body or markdown replacement requires if_match_hash from read_item. Targeted text_edit and section edits use their own expected-content guards. text_edit.source_precondition optionally guards a separate source passage in the same item at commit time, using the selection envelope format. Cannot publish, unpublish, or move an item. To highlight a passage, wrap it in double equals signs: ==like this==. It renders as a real highlight. Bold and italic still mean bold and italic. Use a highlight when someone asks for the important parts to stand out, and mark the few that matter rather than most of the paragraph.

Pass the text as `markdown`. Automated clients should pass an idempotency_key derived from the source event or commit.

Say what to do once and name the items it applies to. Use this instead of repeating update_item when the same change goes to more than one thing: 'tag all of these review', 'move these into Ideas'. A turn has a limited number of steps, so doing twenty items one at a time runs out before it finishes and leaves the job half done. This changes how items are filed and labelled. It never touches what they say, so it needs no content hash. For a change that differs per item - a different sentence in each - read and update them one at a time. Each item is handled on its own and the answer says what happened to each.

The current capture stays visible until the new one lands.

Pass a stable idempotency_key for safe retries.

Its id and path do not change.

Preserves items and RSS subscriptions. Built-in root folders cannot move.

Keeping never removes another reason the item is kept, such as a star or a comment.

The address is fetched and verified before anything is created.

Articles are untouched: nothing is read, kept, or deleted, and Latest, folders, search, and digests do not change.

A soft ranking rule, listed in Settings and undone there: not an unsubscribe, not a filter on Latest, folders, search, digests, or external clients. Topics come from list_reading_sources or the home page's topic strip (ids like source:<folder path>, search:<id>, derived:<id>).

Notes and bookmarks can never be published. This can change what readers can see. Obtain explicit human confirmation immediately before calling it.

This can change what readers can see. Obtain explicit human confirmation immediately before calling it.

Stages a review of every file, folder and inherited access before execution. File contents and identities are preserved. Requires a stable idempotency key. This can change what readers can see. Obtain explicit human confirmation immediately before calling it.

This can change what readers can see. Obtain explicit human confirmation immediately before calling it.

Item and workspace invitations report email delivery status. This can change what readers can see. Obtain explicit human confirmation immediately before calling it.

This can change what readers can see. Obtain explicit human confirmation immediately before calling it.

It disappears from the look pickers and from list_document_templates, and every document and folder already using it keeps rendering exactly as it does now, because template versions are immutable and nothing is deleted. Built-in looks cannot be retired. Use this when someone says a look they made is no longer wanted, rather than leaving a picker full of abandoned experiments. This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.

It stays restorable; this never permanently deletes. This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.

They stay restorable; this never permanently deletes. Use this when someone asks to get rid of more than one thing. Name every item explicitly by id: there is no "everything matching" form, because a request to delete has to say what it is deleting. Each item is handled on its own. One that has changed since you read it, or that has already gone, is reported and the rest still go. The answer says what happened to each. This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.

This cannot be undone and always requires owner approval. This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.

This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.

Restorable; never permanently deleted. This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.

For You falls back to freshness and coverage. This changes or removes existing workspace state. Obtain explicit human confirmation immediately before calling it.