Compared · slack
14 Slack MCP servers. Which one to use.
Every Slack server we index, with whether its source is still reachable and whether we hold a screening verdict. 1 of 14 have a source repository that is no longer publicly reachable.
Scope: 14 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Slack MCP Server | io.github.jtalk22 | no flag | REVIEW | 100 | npm @jtalk22/slack-mcp |
| Slack ↔ WxO MCP Gateway | io.github.markusvankempen | no flag | REVIEW | 95 | npm @markusvankempen/slack-wxo-mcp-gateway |
| io.github.justadityaraj/slack-lists-mcp | io.github.justadityaraj | no flag | REVIEW | 90 | pypi ars-slack-lists-mcp |
| Slack | io.github.mindstone | no flag | REVIEW | 84 | npm @mindstone/mcp-server-slack |
| com.mcparmory/slack | com.mcparmory | no flag | REVIEW | 82 | pypi mcparmory-slack |
| Multi-workspace Slack MCP server with draft+confirm safety, vault auto-export, a | io.github.adelaidasofia | no flag | REVIEW | 82 | not published |
| Slack Explorer MCP | io.github.shibayu36 | no flag | REVIEW | 81 | docker ghcr.io/shibayu36/slack-explorer-mcp:0.12.0 |
| Slack_connect | io.github.pipeworx-io | no flag | REVIEW | 80 | remote endpoint |
| com.pulsemcp/slack | com.pulsemcp | no flag | REVIEW | 79 | npm slack-workspace-mcp-server |
| io.github.CSOAI-ORG/slack-enterprise-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 76 | pypi slack-enterprise-mcp |
| MCP Slack | io.github.crunchtools | no flag | REVIEW | 73 | pypi mcp-slack-crunchtools |
| io.github.stevenvo/slack-mcp-server | io.github.stevenvo | no flag | REVIEW | 63 | pypi slack-mcp-server-v2 |
| ai.waystation/slack | ai.waystation | no flag | REVIEW | 58 | remote endpoint |
| ai.smithery/smithery-ai-slack | ai.smithery | repo unreachable | REVIEW | 64 | remote endpoint |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.