append-blocks
ChatGPTAppend content blocks to an existing note. Without an anchor, the new blocks land at the end of the document. With afterBlockId or beforeBlockId (read these from get-note), the new blocks are inserted at that position. By default this tool returns just the affected slice of the doc plus the new document version; pass returnFullDocument: true to also receive the full updated doc. The "affected slice" (changedContent) is the top-level block(s) covering the insertion — typically just the new blocks themselves, but when the insertion merges into an existing container (e.g. bullets joining an existing list), changedContent includes the parent container so the new IDs are visible in their final structural context.
archive-note
ChatGPTArchive a note. Archived notes are hidden from navigation and search by default. This can also be used to remove a record from a collection, since non-archived collections don't display archived children.
ask-slite
ChatGPTAsk a question and get an AI-generated answer with source citations. A long-running question returns status: "processing" with a threadId — call read-thread with that id to collect the answer. Saves the question and answer to the user's Slite history.
create-channel
ChatGPTCreate a new channel (top-level container for docs). The current user becomes an admin of the channel. Personal channels cannot be created via this tool.
create-collection
ChatGPTCreate a new collection (structured database of docs) with columns. A collection is a note that acts as a database. It has typed columns and each row is a sub-doc (created via create-note). The Title column is always present. Supported column types: select, multi-select, text, number, date, todo, link, users, notes.
create-note
ChatGPTCreate a new note with title and optional content. The sliteml parameter accepts the rich-text format and supports every block type. When creating a note inside a collection, you can also set field values via fields.
edit-document
ChatGPTApply MANY block edits to a single note as ONE atomic change. Use this instead of calling append-blocks / modify-range / remove-blocks repeatedly when you need to touch several places in the same doc — every edit lands (or none does), in one commit, with one version bump. Each entry in edits is one of: - { op: 'insert', afterBlockId | beforeBlockId, sliteml } — insert new blocks at a position (omit both anchors to append at the end). - { op: 'modifyRange', startBlockId, endBlockId, sliteml } — replace a range of blocks (empty sliteml deletes the range); a block the new content edits keeps its ID, and a table keeps it when the content names it, the rows and columns sent replacing all of its own. - { op: 'remove', blockIds } — delete blocks. Read the doc first with get-note to get block ids. Edits should be independent (don't have one edit remove or replace a block another edit also targets). They apply atomically: if any edit can't be applied, the whole batch fails and nothing is committed. Pass dryRun: true to validate and receive the resulting document (slitemlHybrid) WITHOUT committing — useful for previewing. By default the response carries just the new version and the affected changedContent slice; pass returnFullDocument: true for the full updated doc.
get-note
ChatGPTGet a note's content by ID. Returns sliteml (default — includes block IDs needed for editing), markdown, HTML, or collection data. Call this before any partial edit to obtain the block IDs you'll target. Pass startBlockId/endBlockId to fetch only a section of the doc, or fullContent: false + cursor to page through a long doc — both keep responses small when iterating.
get-note-children
ChatGPTList child notes under a parent note, in sidebar order (highest listPosition first). Paginated.
get-user
ChatGPTGet a user by ID. Returns user details including name, email, and role.
get-user-group
ChatGPTGet a user group by ID. Returns group details including name, description, and members.
list-channels
ChatGPTList channels (top-level containers) accessible to the current user. Returns channel names, types, and IDs.
list-empty-notes-for-knowledge-management
ChatGPTList empty notes for knowledge management. Supports pagination and optional owner and channel filters.
list-inactive-notes-for-knowledge-management
ChatGPTList inactive notes for knowledge management. Supports pagination and optional owner and channel filters.
list-notes-for-knowledge-management
ChatGPTList notes for knowledge management. Supports pagination and optional review-state, owner, channel, and time-window filters.
list-public-notes-for-knowledge-management
ChatGPTList public notes for knowledge management. Supports pagination and optional review-state, owner, channel, and time-window filters.
list-recently-edited-notes
ChatGPTList the last 10 notes recently edited by the current user. Returns note titles, IDs, and edit timestamps.
list-recently-visited-notes
ChatGPTList the last 10 notes recently visited by the current user. Returns note titles, IDs, and visit timestamps.
modify-block
ChatGPTReplace a single block in a note. Provide the block's ID via blockId (read it from the trailing {/* #abc123 */} marker on a markdown line, or the id="..." attribute on an XML block, after calling get-note). The new content goes in sliteml and replaces the targeted block in place at its exact path — nested blocks (a list item inside a <ul>, a callout child) are replaced surgically without disturbing the enclosing container. To replace several consecutive blocks at once, use modify-range instead. By default this tool returns just the changed range plus the new document version; pass returnFullDocument: true to also receive the full updated doc.
modify-range
ChatGPTReplace a range of consecutive blocks with new sliteml content. The range runs from startBlockId to endBlockId inclusive and may cross container boundaries (e.g. start inside a list and end inside a following paragraph or callout) — same behavior as a user selecting across blocks and pasting in the editor. Blocks outside the range are preserved. A block the new content edits (most of its words kept, even as another type of text block) keeps its ID and its comments; a table keeps its ID when the new content names it. When to use: rewriting a section, replacing several siblings, or deleting a span of blocks (pass an empty sliteml to delete the range with no replacement). For a single-block edit use modify-block instead. By default this tool returns just the affected slice plus the new document version; pass returnFullDocument: true to also receive the full updated doc. The "affected slice" (changedContent) is the top-level block(s) covering the new range — usually exactly the new content, but when it lands inside an existing container (e.g. a list or callout) the slice may include that container so its IDs are visible in their final structural context. Empty when the range was deleted.
move-note
ChatGPTMove a note into another parent note and/or reposition it among its siblings. The note will become a child of the target parent note. This can be used to reorganize documentation, move pages between channels, or reorder subpages in the sidebar via listPosition.
read-thread
ChatGPTRead an AI thread back as question / answer rounds. Use it to poll a processing response from ask-slite or slite-agent (re-check after retryAfterSeconds), or to read any past conversation the user refers to — thread URLs look like …/app/agent/history/{threadId}, pass the trailing id.
remove-blocks
ChatGPTRemoves one or more blocks from an existing note in Slite by their block IDs. Returns the updated document as sliteml with block IDs. Important: Before using this tool, first fetch the note using get-note with format='sliteml' to see the document structure and block IDs. If a parent block and one of its nested children are both specified, only the parent will be removed (removing a parent already removes its children).
restore-note
ChatGPTRestore an archived note. This reverses the effect of archive-note, making the note visible again in navigation and search. If the note is a collection record, restoring it will make it reappear in the parent collection.
search-notes
ChatGPTSearch notes by keywords. Returns matching notes with titles, IDs, and text highlights.
search-user-groups
ChatGPTSearch and list user groups in the organization. Returns matching groups with names and descriptions.
search-users
ChatGPTSearch and list users in the organization. Returns matching users with names, emails, and roles.
set-note-review-state
ChatGPTSet the review state and/or review owner of a note. Available states: - "none": Clear the review state - "final": Mark the note as verified - "out_of_date": Mark the note as outdated (supports an optional message) - "verification_requested": Request verification for the note (supports an optional message) You can also set the review owner (reviewStateManagedBy or reviewStateManagedByUserGroup) without changing the review state.
slite-agent
ChatGPTInvoke Slite Agent on the workspace knowledge base. Stateful: returns a threadId for follow-ups; can edit / create / organize docs as well as read. Pass threadId from a prior response to continue the same thread — including answering a question the agent asked in its answer. Drafted changes come back as status: "needs-approval" with a triageUrl where a human reviews them — approvals are not actionable over MCP. A long run returns status: "processing" with a threadId — poll read-thread with that id to collect the result; the run keeps working meanwhile.
update-channel
ChatGPTUpdate a channel. Supports renaming and changing the channel icon. Renaming also renames the channel doc.
update-collection
ChatGPTUpdate the columns of a collection (structured database of docs). Important: Always use get-note with format "collection" first to see the current columns and their IDs before updating. Supported column types: select, multi-select, text, number, date, todo, link, users, notes. Use columns to add new columns. Use removeColumns to remove columns by ID. Removing a column deletes all its data from every record. Columns not mentioned in either parameter are left unchanged.
update-note
ChatGPTUpdate an existing note. Can update title, replace rich-text content via sliteml, and/or set collection record field values. IMPORTANT: sliteml fully replaces the existing rich-text body. For partial edits, use modify-block / modify-range / append-blocks (call get-note first to obtain block IDs).
update-table
ChatGPTMake a STRUCTURED edit to an in-document table (a table embedded in a doc's body) without re-emitting the whole table. Use this instead of modify-block/modify-range when you want to change a cell, tag, row, or column of an existing table — it is far less error-prone than rewriting the table's sliteml. First call get-note (sliteml) to read the table: its block id is the id on the <database> element, column ids are the key on each <column>, and row ids are the key on each <record>. Operations (provide any combination): - columns: add new typed columns. Column types are identical to create-collection/update-collection — select, multi-select, text, number, date, todo, link, users, notes. - removeColumns: remove columns by id (deletes their data in every row). A table keeps at least one column: an edit that would leave none is refused. - setCells: set a cell's value (for select/multi-select pass the option label(s); for a text column pass the cell's content). - addRows: append rows, optionally with initial fields keyed by column id. - removeRows: delete rows by id. A table keeps at least one row: deleting them all leaves one empty row. To delete the table itself, remove its block with remove-blocks or edit-document. setCells/addRows fields support select, multi-select, text, number, date, todo, and link columns. Text (rich-text) cells work too — their content lives in the document body, and update-table writes it there for you in the same atomic edit, so you never need to re-emit the table's sliteml. To set a users or notes cell, first resolve the people/docs with search-users / search-notes, then pass the value as a JSON array of the objects those tools return — e.g. [{"id":"<userId>","displayName":"...","email":"..."}] for users, [{"id":"<noteId>","title":"..."}] for notes. Each ref needs at least an id. Pass [] to clear the cell. This is for plain in-document tables. To edit a COLLECTION (whose rows are sub-docs), use create-note/update-note with fields and update-collection instead.
upload-file
ChatGPTPrepare a file or image upload into a note, without passing the bytes through the model. Workflow: 1. Call this tool with the target noteId, filename, contentType and exact byte size. 2. PUT the raw file bytes to uploadUrl outside MCP, sending every header in uploadHeaders verbatim. Do not base64-encode or transform the file: use curl -X PUT --data-binary @path -H "Content-Type: ..." -H "Content-Disposition: attachment" "<uploadUrl>" or fetch(uploadUrl, { method: 'PUT', headers: uploadHeaders, body: blob }). 3. Embed the returned sliteml block in the note with append-blocks, modify-block, modify-range or update-note. Add a caption="..." attribute if the user wants one. The block shows as broken until the PUT has completed. To use an image as the doc's cover banner instead, pass its mediaId to update-note's coverMediaId. The signed uploadUrl expires after uploadExpiresAt; call the tool again if it did. Prepare, PUT and embed one file at a time. Images are capped at 20 MB, or the organization's lower plan-specific attachment size limit. Other files use the plan-specific limit. All uploaded files count toward the organization's storage limits, so avoid duplicate or unnecessary uploads. This tool is limited to 20 calls per minute and 60 calls per 10 minutes per user. To embed an image that already has a public URL, skip this tool and write <image url="https://..." /> (or markdown ) directly — Slite fetches and stores a copy.
verify-note
ChatGPTMark a note as verified. Optionally set an expiration date for the verification.
append-blocks
Claudearchive-note
Claudeask-slite
Claudecreate-channel
Claudecreate-collection
Claudecreate-note
Claudeedit-document
Claudeget-note
Claudeget-note-children
Claudeget-user
Claudeget-user-group
Claudelist-channels
Claudelist-empty-notes-for-knowledge-management
Claudelist-inactive-notes-for-knowledge-management
Claudelist-notes-for-knowledge-management
Claudelist-public-notes-for-knowledge-management
Claudelist-recently-edited-notes
Claudelist-recently-visited-notes
Claudemodify-block
Claudemodify-range
Claudemove-note
Clauderead-thread
Clauderemove-blocks
Clauderestore-note
Claudesearch-notes
Claudesearch-user-groups
Claudesearch-users
Claudeset-note-review-state
Claudeslite-agent
Claudeupdate-channel
Claudeupdate-collection
Claudeupdate-note
Claudeupdate-table
Claudeupload-file
Claudeverify-note
Claude