There is no official Slack MCP server in the registry.
As of the 2026-10-03 registry snapshot (38,152 indexed servers), no entry is published under a Slack-owned namespace (com.slack, io.github.slackapi, io.github.slackhq).
8 community servers use the Slack name. None is published by Slack; treat each as the third-party project it is.
- io.github.aaronsb/slack-mcpupdated 2026-10-01
- io.github.sadri-dridi/slack-channel-okupdated 2026-09-09
- io.github.sadri-dridi/slack-webhook-shapeupdated 2026-09-08
- io.github.nileshpatil6/telegram-slack-mcpupdated 2026-08-31
- io.github.jtalk22/slack-mcp-serverupdated 2026-08-24
- io.github.CSOAI-ORG/slack-enterprise-mcpupdated 2026-08-19
- io.github.mindstone/mcp-server-slackupdated 2026-08-06
- io.github.markusvankempen/slack-wxo-mcp-gatewayupdated 2026-07-19
The registry verifies namespace ownership, so a registered vendor entry is the one identity an agent can pin. Without one there is no verified Slack namespace, no canonical entry to pin a tool contract against, and no drift history when the tool surface changes. A server using the name may still be useful; it is just not Slack speaking.
How mcpindex evaluates what a server declares versus what it does is covered in the methodology and the trust model.
Publishing to the MCP registry gives your users a verifiable namespace. mcpindex syncs the registry daily; a published entry replaces this page with a normal server page, which you can then claim.