slack-mcp-server

Adoption judgment: this is worth considering if your team already uses an MCP client and wants AI agents to act inside Slack for tasks like reading, searching, and sending messages. But the current evidence mostly comes from the official GitHub repository, which shows the project exists and has some attention; it does not strongly prove broad production reliability. GitHub stars and forks are attention proof, not usability proof.

In practice, it is better understood as a protocol adapter that exposes Slack capabilities to AI agents through MCP. It is not a full AI workplace assistant, and it is not Slack's native bot platform itself. A more accurate analogy is: an open-source server that wraps Slack API actions as MCP tools so MCP-compatible clients can call them in a standardized way.

On cost and setup, the evidence supports only a conservative view: it is open source, requires self-hosting, Slack bot token and permission setup, and an MCP-compatible client. The official repository evidence does not provide hosted pricing, SaaS plans, or dependable API cost guidance, so “open source” should not be read as “no implementation cost.