[ MCP SERVER SUMMARY ]
Slack MCP server summary
Slack's official remote MCP server gives AI agents access to workspace conversations, search, messaging, and canvases under each user's Slack permissions. Bifrost connects to https://mcp.slack.com/mcp with your Slack app's client credentials so tool access is centralized and auditable.
| Property | Details |
|---|---|
| Company | Slack |
| Connection type | HTTP |
| Authentication | OAuth 2.0 (confidential Slack app) |
| Package or endpoint | https://mcp.slack.com/mcp |
| Capabilities | Search messages and files, Read channel history, Send messages and manage canvases |
| Official documentation | Slack MCP documentation |
Before you start
- A Slack app with MCP-compatible OAuth (client ID and secret)
- Workspace approval for the app where required
What you can do with Slack
- Connect Claude or Cursor to Slack without per-developer token sprawl
- Allow search but block chat:write for read-only research agents
- Meet enterprise requirements for AI access to Slack data
[ HOW TO CONNECT ]
Connect Slack to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Slack in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose HTTP. Or register via the API below.
• Streamable HTTP only — Slack does not support SSE or Dynamic Client Registration.
• Register a Slack app and supply client_id / client_secret for confidential OAuth.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Slack.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Slack via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "slack",
"connection_type": "http",
"connection_string": "https://mcp.slack.com/mcp",
"auth_type": "oauth",
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Slack through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Slack MCP server do?
Slack exposes search messages and files, read channel history, send messages and manage canvases to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Slack authenticate when used with Bifrost?
Slack uses OAuth 2.0 (confidential Slack app). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Slack through Bifrost?
Yes. After registering Slack in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Gmail
Connect AI assistants to Gmail to search messages, draft and send email, and automate inbox workflows through Google Workspace MCP.
Google Chat
Enable AI assistants to work with Google Chat spaces, messages, and collaboration workflows through Google Workspace MCP.
Intercom
Connect AI assistants to Intercom customer support data and workflows through Intercom’s MCP integration.