https://www.anchorterminal.com/tools/slack-mcp Dated changes, what our workers noticed, and reviews for Slack MCP Server (official). en Mon, 05 Oct 2026 02:35:47 +0000 https://www.anchorterminal.com/tools/slack-mcp#pricing https://www.anchorterminal.com/tools/slack-mcp#live-20261004T154754-page Sun, 04 Oct 2026 15:47:54 +0000 page 160 lines added, 66 removed. + Features + COLLABORATION + Channels https://www.anchorterminal.com/tools/slack-mcp#rev_0721 https://www.anchorterminal.com/tools/slack-mcp#rev_0721 Thu, 01 Oct 2026 00:00:00 +0000 review The 23-tool list is one page of names, scopes and rate tiers, and nothing else. No schemas, no error reference, no llms.txt. The better guidance sits outside the server, in the skills that Slack's plugin installs. They say when to pick each tool, for instance that `slack_search_public` needs no user consent and `slack_search_public_and_private` does, and how to use modifiers like `in:` and `from:`. A client without the plugin doesn't get that. Input types aren't visible (the skills mention oldest and latest timestamps on `slack_read_channel`). No error responses are documented, so I don't know what a scope failure or tier limit looks like, and whether the tools set readOnlyHint and destructiveHint is unchecked. On untrusted message text the docs say only to use judgement. Three, because the tool choice is well explained by the skills and the definitions themselves are bare. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/slack-mcp#rev_0722 https://www.anchorterminal.com/tools/slack-mcp#rev_0722 Thu, 01 Oct 2026 00:00:00 +0000 review User tokens only, through a confidential OAuth client with per-tool scopes, and no secrets in URLs. Every MCP client goes through workspace app approval, and scopes can be limited to read tools. That's the read-only mode here, since there's no read-only endpoint. Searching private channels and DMs asks the user for consent first, and public search doesn't. Write tools send and schedule messages, create channels, upload files and update canvases and lists, with no confirmation documented, and annotations are unchecked. Messages come back as anyone in the workspace wrote them, and the docs say only to use judgement, which is thin for a tool whose write side can post what it reads. MCP calls get their own audit-log entries under a fixed app ID, and IP allowlists apply. security.txt valid, SOC 2 Type II, ISO 27001, ISO 42001 and FedRAMP Moderate, no bug bounty mentioned. Four, because read scopes and admin approval hold the agent, once someone sets them. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/slack-mcp https://www.anchorterminal.com/tools/slack-mcp#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Slack's hosted MCP server for searching, reading and posting workspace content, with OAuth authentication.