Connect your AI assistant to Slite using the Model Context Protocol (MCP) — an open standard that lets AI tools interact with external services.
One connection gives your AI assistant the ability to search your knowledge base and connected sources, and to read, write, and organize docs — all from inside Claude, Cursor, ChatGPT, or any MCP-compatible tool.
Formerly Super: The search and cross-source capabilities in the Slite MCP were previously available as a separate product called Super (also known as the Super MCP or External Search MCP). Super has been deprecated and is no longer available as a standalone product. All of its functionality is now included in the unified Slite MCP at
https://api.slite.com/mcp.
What is MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants like Claude, ChatGPT, Cursor, or Gemini connect to external tools and data sources. Instead of copy-pasting context into a chat window, your AI assistant can directly read from and write to connected services.
Slite has one MCP that covers both search and writing — no need to choose between integrations.
What can I do with the Slite MCP?
Ask your AI assistant questions answered by your Slite docs
Search across your docs and return answers
Pull knowledge from connected sources (Google Drive, Slack, Linear, etc.)
Search across all your connected data sources simultaneously
Create or update docs in Slite from your AI assistant
Draft, edit, and organize docs directly in your workspace
Organize or manage your knowledge base via AI
Move, archive, verify, and restructure docs
Do all of the above in one workflow
Yes — it's all one MCP, one connection
Yes — it's all one MCP, one connection
Why use the Slite MCP?
Get instant answers from across all your connected data sources
Instead of searching through multiple platforms yourself (Google Drive, Slack, Linear, etc.), ask your AI assistant and it'll search across all your connected data sources simultaneously to find the answers you need.
Your team spends less time platform-hopping and more time using information.
Turn existing knowledge into reusable content
Pull information from across your workspace to create new onboarding guides, customer announcements, or internal reports.
What used to take hours of research and writing now takes minutes.
Work where you already work
Interact with your Slite workspace directly from your favorite AI assistant — no context switching, no copy-pasting.
Example prompts
These are example prompts you could send to your AI assistant once the Slite MCP is connected:
- "Summarize our Q1 product updates and draft a customer announcement."
- "What's our policy on remote work?"
- "Draft an onboarding guide using our internal discussions and meetings."
Setting it up
The Slite MCP uses OAuth authentication — no API keys or config files needed. Just add the following URL as a custom MCP connector in your AI assistant's settings:
https://api.slite.com/mcp
The Slite MCP works with Claude, ChatGPT, Cursor, Gemini, Codex, and any other tool that supports the Model Context Protocol.
With Claude Desktop
Go to Settings > Connectors > Add custom connector , then enter the Slite MCP URL above as well as a name. The advanced settings can stay blank.
Sign in to your Slite account and authorize Claude.
With ChatGPT/Codex
In the web app, go to Settings > Apps > Advanced Settings , and enable Developer Mode .
Create a new app with the Slite MCP URL:
https://api.slite.com/mcpSelect the OAuth authentication option and leave the other fields blank.
Sign in to your Slite account and authorize ChatGPT.
With other MCP clients
Add
https://api.slite.com/mcp as a remote MCP server URL and complete the OAuth authentication when prompted.The local (self-hosted) MCP server option has been deprecated and is no longer supported. The remote endpoint
https://api.slite.com/mcp is the only supported option.
Supported Tools
Here are the tools you can currently use through Slite MCP.
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)
get-comment-thread-on-note
Retrieve a specific comment thread on a doc, including all replies
get-note
Retrieve full content of a specific doc
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
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
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 or content of existing docs
verify-note
Mark a doc as verified
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.