This page lists the tools available through the Slite MCP and explains how to use them. To connect your AI assistant first, see Slite MCP .
Supported Tools
Here are the tools you can currently use through Slite MCP. The Slite MCP offers 43 tools for reading and writing to your workspace.
append-blocks
Add content blocks to existing docs
archive-note
Archive a doc
ask-slite
Get answers from your docs
create-channel
Create a new channel (top-level container for docs)
create-collection
Create a collection database with columns
create-comment-thread
Start a new comment thread on a doc, optionally anchored inline to a specific text span
create-note
Create new docs (with optional parent/channel)
edit-document
Apply multiple block edits to a doc as one atomic change
get-comment-thread-on-note
Retrieve a specific comment thread on a doc, including all replies
get-note
get-note-children
List all sub-docs under a parent
get-user
Get user details by ID
get-user-group
Get user group details by ID
list-channels
List all accessible channels in workspace
list-comment-threads
List comment threads on a doc, with filtering by resolved/unresolved state
list-empty-notes-for-knowledge-management
List empty docs for knowledge management cleanup
list-inactive-notes-for-knowledge-management
List inactive docs for knowledge management cleanup
list-notes-for-knowledge-management
List docs with knowledge management filters
list-public-notes-for-knowledge-management
List public docs for knowledge management
list-recently-edited-notes
Show docs you recently edited
list-recently-visited-notes
Show docs you recently viewed
modify-block
Edit a specific block within a doc, in place
modify-range
Replace a range of consecutive sibling blocks within a doc
move-note
Move a doc to a different channel or parent
read-thread
Read an AI thread back as question and answer rounds
request-change
Open a change request: an agent reads the docs you name, turns your command into proposed changes, and leaves them as approval cards for a human to review in Slite
read-change-request
Read the status of a change request opened with request-change (processing, pending_review, completed, no_changes or failed)
remove-blocks
Delete specific blocks from a doc
reply-to-comment-thread
Post a reply to an existing comment thread
resolve-comment-thread
Mark a comment thread as resolved
restore-note
Restore an archived doc
search-notes
Find docs by keyword across your workspace
search-user-groups
Find user groups by name
search-users
Find users by name or email
set-note-review-state
Set the review state and/or review owner of a doc
slite-agent
Run Slite Agent across your workspace knowledge base
unresolve-comment-thread
Reopen a previously resolved comment thread
update-channel
Update a channel's name, icon, or visibility
update-collection
Add or remove columns in a collection database
update-note
Update title, content, or cover banner of existing docs. (To set a cover banner, first upload the image with upload-file to get its mediaId, then pass that as coverMediaId.)
update-table
Make a structured edit to a table inside a doc
upload-file
Upload a local image or file and embed it in a doc
verify-note
Mark a doc as verified
Controlling note order
The create-note, update-note, and move-note tools accept an optional
listPosition to control where a doc appears among its siblings in the sidebar:top— place it firstbottom— place it last- A positive number — set a precise position; higher values appear first
To insert a doc between two siblings, read their positions with get-note or get-note-children, then use the midpoint. For example, between positions
200 and 100, use 150.get-note returns a doc's effective
listPosition. get-note-children returns each child's effective position and lists children in the same order as the Slite sidebar (highest position first).Reading large docs
Some MCP clients cap how big a single tool response can be. On a large doc, especially one with many tables, a full get-note response can go over that limit and get cut off. The sliteml format is the one that includes block IDs, and it's larger than the markdown export of the same doc. So when the response is cut off, the block IDs past that point are missing, and your assistant can't edit those blocks.
get-note has two ways to keep responses small:
Fetch one section by block ID
startBlockId— return the doc from this block onward (inclusive)endBlockId— return the doc up to and including this block
Use one or both to fetch a specific range. Both only apply when
format is sliteml.Page through the doc
fullContent: false— return only the first part of the doc (about 2,000 characters, ending on a block boundary), plushasMoreandnextCursorcursor— pass thenextCursorvalue from the previous response to get the next part
Repeat until
hasMore is false. fullContent is ignored when startBlockId or endBlockId is set.Don't see these options in your AI assistant? All the parameters above are included in the tool definitions the Slite MCP publishes. If your client only shows
noteId and format for get-note, it may be using an older copy of the tool list. Try refreshing or reconnecting the Slite connector. Note that fullContent must be sent as a true/false (boolean) value, not as the text "false".Uploading files and images
The upload-file tool lets your AI assistant put a local image, plot, screenshot, or PDF straight into a doc. The file is sent directly to Slite storage instead of passing through the AI model, so large files work too.
Your assistant calls upload-file with the target doc, file name, type, and size.
Slite returns a short-lived signed upload link, and your assistant sends the file to it.
The file is embedded as a block in the doc.
Good to know
- File size follows your plan. Uploads go through the same size check as any other file attached to a doc: 10 MB on Free and Solo, 200 MB on Basic and trials, and unlimited on Pro and Enterprise. Images are capped at 20 MB. There is no separate size limit for MCP uploads.
- The file block can look broken for a moment. It stays broken until the upload finishes — refresh the doc if it still looks that way.
- The upload link expires. If the upload doesn't complete in time, your assistant has to request a new link and try again.
- You need edit access to the target doc. The file inherits that doc's permissions, so anyone who can see the doc can see the file.
- Uploads count toward your workspace's storage.
- Uploads are rate limited to 20 per minute and 60 per 10 minutes, per user.
- Files that already have a public URL don't need uploading. Your assistant can embed the URL directly, and Slite saves its own copy.
Managing Tools
You may be able to control which tools your AI assistant can access, depending on your client.
For Claude Desktop
- Go to Settings > Connectors > Slite > Configure, then review when Claude is allowed to use the tools.
- Always allow — Claude can use this tool without prompting you
- Needs approval — Claude will ask before using this tool
- Blocked — Claude cannot use this tool
For other MCP clients
Tool management varies by client. Check your AI assistant's documentation to see if and how you can enable or disable individual tools for a connected MCP server.