Slack MCP Server
ai.waystation/slack
answering
Slack is answering right now. Last checked 15 min ago. Last commit 10 Sep 2025.
Send messages, access channels, and manage files in your Slack workspace.
Uptime history
39 hours of history
39 hours agonow
100.0%
Uptime 24h
182 of 182 checks
—
Tools
hidden behind auth
622 ms
Response time
average over 24h
58
Stars
last commit 10 Sep 2025
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.
run in your terminal
claude mcp add slack --transport http https://waystation.ai/slack/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"slack": {
"url": "https://waystation.ai/slack/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.slack]
url = "https://waystation.ai/slack/mcp".cursor/mcp.json
{
"mcpServers": {
"slack": {
"url": "https://waystation.ai/slack/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"slack": {
"url": "https://waystation.ai/slack/mcp"
}
}
}This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://waystation.ai/slack/mcp | streamable-http | needs key | 905 ms | 15 min ago |
| https://waystation.ai/slack/mcp/sse | sse | needs key | 3733 ms | 15 min ago |
Slack — questions
Answers built from our own checks of this server.
Why is there no tool list for Slack?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Slack working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 622 ms. The bar chart above shows every period we have measured.
How do I connect Slack?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Slack need an API key?
Yes. Every time we knock, Slack answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Slack?
It answers our handshake in 622 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Slack open source?
Yes — written in JavaScript, 58 stars on GitHub and 2 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.