Overview
Tool catalogue
Slack tools are surfaced through the MCP runtime (POST /api/v1/mcp/:serverId) and the HTTP chat endpoint (POST /api/v1/mcp/:serverId/chat). In router mode the model uses SEARCH_TOOLS to discover the right slug at runtime — you don’t bind a fixed REST resource ahead of time. The catalogue covers:
Discover the full list at runtime:
SEARCH_TOOLS({query: "post message"}) and stream the matched slugs back.
Connect setup
Slack uses OAuth 2.0 with PKCE against a Slack-registered app. One app per platform is enough — your end users authorise their own workspace by going through Slack’s consent screen.1
Create a Slack app
Go to api.slack.com/apps → Create New App → From scratch. Under OAuth & Permissions, copy the Client ID and Client Secret.
2
Add the redirect URL
Under OAuth & Permissions → Redirect URLs, add:
3
Configure bot & user scopes
Add the bot token scopes your integration needs — e.g.
channels:read, channels:history, chat:write, users:read, reactions:write, files:read, files:write, pins:write, reminders:write. Message search additionally requires the search:read user scope.4
Connect via the widget
The end user opens the Connect widget, picks Slack, and is sent through Slack’s consent screen to authorise the workspace.
Usage
Through the chat endpoint (recommended)
SLACK_CHAT_POST_MESSAGE / SLACK_FETCH_CONVERSATION_HISTORY and streams results back as SSE.
Direct MCP JSON-RPC (Claude Desktop / Cursor / custom MCP clients)
tools/call JSON-RPC method.