Slite MCP

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.
﻿
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?
The Slite MCP can…
Search across your docs and return answers
Search across all your connected data sources simultaneously
Draft, edit, and organize docs directly in your workspace
Move, archive, verify, and restructure docs
Upload files from your machine straight into a doc
Do all the above via one MCP, one connection
﻿
Why use the Slite MCP?Get instant answers from across all your connected data sourcesInstead 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 contentPull 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 workInteract with your Slite workspace directly from your favorite AI assistant — no context switching, no copy-pasting.
Example promptsThese 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."
"Upload this chart and add it to our weekly metrics doc."
﻿
Setting it upThe Slite MCP uses OAuth authentication, so no API keys are needed. Most AI assistants just need the URL below. A few need a quick extra setup step, covered in the sections below.
https://api.slite.com/mcp
The Slite MCP works with Claude, ChatGPT, Cursor, the Gemini app, Google Antigravity, Gemini Enterprise, Codex, and any other tool that supports the Model Context Protocol.
With Claude DesktopGo to Settings > Connectors > Discover > Search for Slite, or go direct to the  Slite Connector page .
Click "Connect to Claude".
Sign in to your Slite account and authorize Claude.
With ChatGPTIn the ChatGPT web app, go to Settings > Security and login and turn on Developer Mode.
Go to Settings > Plugins. With Developer Mode on, a + icon appears — click it to add a custom plugin.
Give it a name and enter the Slite MCP URL: https://api.slite.com/mcp
Select OAuth authentication and leave the remaining fields blank.
Sign in to your Slite account and authorize ChatGPT.
Open a new chat and enable Slite for that conversation from the tools menu. Connectors added in Settings are available to your account, but each conversation decides which tools it can call — and existing conversations won't pick up a newly added connector.
Test it with a prompt like "Use Slite to search for recent docs."
With CursorAdd Slite to Cursor
On Mac, open Terminal and run the following command:
mkdir -p ~/.cursor && cat > ~/.cursor/mcp.json << 'EOF'
{
  "mcpServers": {
    "slite": {
      "url": "https://api.slite.com/mcp"
    }
  }
}
EOF
Note: this command replaces the contents of the file. If you've already added other MCP servers to Cursor, add the slite entry to your existing ~/.cursor/mcp.json file instead.
On Windows, create a file called mcp.json in the .cursor folder of your user directory ( %USERPROFILE%\.cursor\mcp.json ) and paste in the following. If the file already exists, add the slite entry to it instead.
{
  "mcpServers": {
    "slite": {
      "url": "https://api.slite.com/mcp"
    }
  }
}
Connect your account
Fully quit Cursor (Cmd+Q on Mac) and reopen it.
Start a new chat and ask the Agent to use Slite, for example "Use Slite to list my channels."
When the Connect with slite card appears, click Authenticate. Sign in to your Slite account and authorize Cursor.
Cursor will then complete your request.
The sign-in prompt only appears the first time Cursor uses Slite, not when you add the server.
With CodexOpen Terminal and run the following command:
codex mcp add slite --url https://api.slite.com/mcp
Note: run this in Terminal, not inside a Codex session. Codex can't change its own settings from within a session.
A browser tab opens. Sign in to your Slite account and authorize Codex. When you see "Successfully logged in." in Terminal, you're connected.
Start Codex and test it with a prompt like "Use Slite to list my channels."
This also connects Slite to Codex in the ChatGPT desktop app, since it shares the same settings.
With the Gemini app (personal Google accounts)Personal Google accounts can add Slite as a custom connector in the Gemini app. Work (Google Workspace) accounts can't add custom connectors yet. If you use Gemini with a work account, see With Google Antigravity below.
Go to  gemini.google.com/customize/connectors  and click + Custom in the top right.
Enter the Slite MCP URL: https://api.slite.com/mcp. Leave the Client ID and Client secret fields under Additional settings blank.
Click Next. The first click shows a Copy redirect URI button, which you don't need. Click Next again to continue.
Accept Google's notice about third-party apps, then click Agree and continue to link your accounts.
Sign in to Slite, choose your workspace, and authorize Gemini.
On Save your custom app, keep the name "Slite" and click Connect.
Start a new chat and test it with a prompt like "Use Slite to list my channels."
Slite appears under Custom apps at the bottom of the Connected Apps page, not under Installed. Gemini may ask permission before using some tools, such as Slite Agent. Choose Always allow to skip the prompt next time.
With Google AntigravityIf you use Gemini with a work (Google Workspace) account, use Google Antigravity instead. It's a desktop app that works like a chat.
Add Slite to Antigravity
Download and install  Google Antigravity , then sign in with your Google account.
Open Terminal and run the following command:
mkdir -p ~/.gemini/config && cat > ~/.gemini/config/mcp_config.json << 'EOF'
{
  "mcpServers": {
    "slite": {
      "serverUrl": "https://api.slite.com/mcp"
    }
  }
}
EOF
Note: this command replaces the contents of the file. If you've already added other MCP servers to Antigravity, add the slite entry to your existing ~/.gemini/config/mcp_config.json file instead.
Connect your account
Fully quit Antigravity (Cmd+Q on Mac) and reopen it.
Click Customizations in the left sidebar and open the Installed tab.
Find slite and click Authenticate. Sign in to your Slite account and authorize Antigravity.
Start a new conversation and test it with a prompt like "Use Slite to list my channels."
With other MCP clientsAdd https://api.slite.com/mcp as a remote MCP server URL and complete the OAuth authentication when prompted.
With Gemini Enterprise (or other clients requiring manual credentials)Some clients do not support automatic Dynamic Client Registration (DCR) and require you to manually provide a Client ID, Client Secret, and OAuth endpoints.
Step 1: Register a client via DCR
Run the following command in your terminal, replacing <your-redirect-uri> with your client's OAuth redirect URI:
curl -X POST https://slite.com/api/mcp/oauth/register \
  -H "Content-Type: application/json" \
  -d '{
    "client_name": "Gemini Enterprise",
    "redirect_uris": ["<your-redirect-uri>"],
    "response_types": ["code"],
    "grant_types": ["authorization_code", "refresh_token"],
    "token_endpoint_auth_method": "client_secret_post"
  }'
The response will return your client_id and client_secret.
Step 2: Configure your client with the endpoint values
Field
Value
Issuer
https://slite.com/api/mcp/oauth
Authorization Endpoint
https://slite.com/api/mcp/oauth/auth
Token Endpoint
https://slite.com/api/mcp/oauth/token
Registration Endpoint
https://slite.com/api/mcp/oauth/register
Userinfo Endpoint
https://slite.com/api/mcp/oauth/me
JWKS URI
https://slite.com/api/mcp/oauth/jwks
MCP Server URL
https://api.slite.com/mcp
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.
For the full list of tools and how to use them, see  Slite MCP: Tools⁠ .