Slack — how agent-ready is it?
A mature API with an official MCP endpoint — but 2025's rate-limit crackdown on non-Marketplace apps showed Slack will squeeze third-party agents when it suits the platform.
API surface — 8/10
Web API covers messaging, channels, users, files; Events API and Socket Mode for real-time.
MCP / agent protocol — 8/10
Official remote MCP endpoint launched in 2026 alongside the broader platform-vendor wave.
Docs quality — 8.5/10
api.slack.com is well-organized with per-method scopes and limits.
Auth friction — 6.5/10
Granular bot scopes are good, but workspace-admin approval and app-directory review add real friction for agent installs.
Rate limits & pricing fairness — 6/10
2025 tightened rate limits sharply for non-Marketplace apps (notably conversations.history) — internal agents got collateral damage.
ToS stance on agents — 7/10
Bots are native citizens, but data-export and external-LLM clauses constrain what an agent may do with content.
Machine-readable output — 8.5/10
Everything JSON; block kit is structured; webhooks mature.
Stability — 6.5/10
The 2025 rate-limit change broke working integrations with short notice — a real strike against trust.
Sources
Point-in-time assessment — platforms change their API terms often (that volatility is itself scored under Stability).
- api.slack.com/apis — API documentation (accessed 2026-07-12)
- api.slack.com/changelog — Rate-limit changes for non-Marketplace apps (2025) (accessed 2026-07-12)
- github.com/modelcontextprotocol/servers — MCP servers directory — official vendor servers (accessed 2026-07-12)
- api.slack.com/apis/rate-limits — Rate limit tiers (accessed 2026-07-12)