Agentifact assessment — independently scored, not sponsored. Last verified Mar 6, 2026.
Slack MCP
Official Slack MCP server. Send messages, read channels, manage threads. Requires workspace OAuth setup.
Viable option — review the tradeoffs
You need your AI agent to read Slack channels, post messages, and manage threads without manual copy-pasting or building custom API integrations.
Solid real-time access with caching and pagination; respects Slack rate limits but requires careful permission scoping to avoid blocks.
You want AI-powered Slack automation like channel summarization, threaded replies, or reaction management in team workflows.
Reliable for core messaging; some advanced features may need env flags enabled; GA since 2026 with enterprise security.
Slack Workspace OAuth Setup
Requires creating a Slack app, requesting specific scopes, and obtaining bot token—non-trivial for agents needing live workspace access without custom auth.
Rate Limits and Permissions
Bound by Slack API tiers; critical actions like posting disabled by default and need explicit env enabling; private channels require invites.
Token Scope Overreach
Broad scopes can trigger Slack security reviews or blocks; stick to minimal required permissions and test in dev workspace to avoid production disruptions.
Trust Breakdown
What It Actually Does
Slack MCP lets AI assistants securely connect to your Slack workspace to search messages and files, read channels, send replies, and manage canvases using natural language.[1][3] It requires setting up OAuth for your workspace to control access.[1]
Official Slack MCP server. Send messages, read channels, manage threads. Requires workspace OAuth setup.
Fit Assessment
Best for
- ✓messaging
- ✓search-retrieval
- ✓file-operations
- ✓user-management
- ✓channel-management
Score Breakdown
Protocol Support
npx -y @modelcontextprotocol/server-slackCapabilities
Governance
- permission-scoping
- rate-limiting