Comparison
Use official or self-host when ownership is solved. Use managed Cloud when rollout and continuity are the real problem.
This page exists to make the operator decision explicit. The official Slack path is real. The commercial wedge now is managed rollout, buyer review, multi-client setup, workflow packaging, and operating continuity.
The market changed in February 2026
Slack launched an official MCP server and a Real-time Search API on February 17, 2026. That changes the wedge. The decision is no longer “Slack MCP or nothing.” It is “official or self-host is enough” versus “managed rollout and reliability is worth paying for.”
Use official or self-host when
- Your team already owns runtime, deployment, and token lifecycle internally.
- Buyer review and rollout sequencing are already handled inside your org.
- You need the full 21-tool OSS surface and want direct operator control.
- You are comfortable treating Slack MCP as infrastructure you maintain yourself.
Use managed Cloud when
- You want one remote endpoint with hosted credential handling and plan-aware account state.
- You need deployment review, procurement-ready security review, or bounded rollout help.
- You want Claude-first setup with Gemini CLI as a supported second path.
- You care about named workflow outcomes such as summary, action items, decisions, support triage, incident summary, and handoff summary.
Decision matrix
- Official / self-host: better when transport ownership is already solved and you don't need the AI brain.
- Free ($0): try the AI brain with monthly credits, no card.
- Pro ($9/mo): better when one operator wants unlimited AI tools and scheduled morning catch-up DM (rolling out Q2 2026).
- Team ($49/mo) flat: better when 2-10 people share the workflow surface and need synced profiles plus audit log.
- Ops (from $199/mo (custom)): better when SLA, custom retention, SOC2 evidence, or multi-tenant isolation become hard requirements.
Commercial and compliance reality
Slack's developer terms matter if the product is commercially distributed. The right near-term move is not to out-"official" Slack. It is to out-operate the official path on workflow continuity, structured outputs, and the daily morning catch-up DM (rolling out Q2 2026) that the official path doesn't ship.
Named workflow outcomes
The commercial layer is not “more CRUD.” It is a productized workflow layer for support triage, incident comms, founder briefings, and product ops, backed by rollout and support boundaries.
Next step
If the team already knows it wants managed rollout, use first-party checkout for Solo or Team. If the team is still deciding whether official/self-host is enough, keep that conversation on the hosted surface with deployment review and procurement.