MCP server
Slack
A legacy archived reference server that should not be installed for a new workshop workflow.
Not made by the vendor. Read what it does before you run it.
What it can access
A Slack bot token can expose channel history and permit posting where the bot is installed.
Security note
The cited reference implementation is archived. Do not install it for a new workshop workflow. Prefer Slack's current official AI integrations or a reviewed vendor connector with channel-level controls.
Do you need it?
No for this archived implementation. Keep the page so old links still resolve, but do not use it as a current installation guide.
Capability and permissions
The legacy server used a Slack bot token to read channel history and post messages where the bot was installed. Those are high-impact permissions.
Least-privilege setup
As of 2026-09-01, the cited Model Context Protocol reference server is archived. Do not install it. If Slack access is genuinely required, ask the Slack administrator to evaluate a current official or vendor-reviewed integration with one test channel and no message-posting permission at first.
Harmless success test
No test is recommended for the archived server. A replacement should be tested only in a new channel with invented messages and no real participants.
Disable, revoke, remove
If previously installed, remove its client configuration, stop the process, revoke the Slack bot token, remove the Slack app, and review channel and app audit logs.
When not to connect
Do not connect source, legal, safeguarding, personnel, incident-response, or private leadership channels. Do not run archived code with a live workspace token.