SlackMCP
Related Servers
Alternatives to SlackMCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables AI agents to read and write Slack messages as the user, not as a bot, using Slack user tokens for authentic actions across multiple workspaces.101MIT
- FlicenseNot gradedqualityDmaintenanceA Slack MCP server that gives AI assistants tools to read, search, and interact with Slack workspaces.-
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that enables AI assistants to access Slack workspace data, including channels, messages, threads, and user information.49,032 npm3MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Slack workspace integration. This server allows AI assistants to interact directly with your Slack workspace, providing tools to manage channels, send messages, list users, and upload files.49,032 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Slack that enables AI agents to interact with Slack workspaces, including listing channels, reading and posting messages, searching, managing users, reactions, and user groups.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that gives AI agents access to your Slack workspaces using session tokens.2MIT
TDQS
Scored across 11 tools
Tools mostly target distinct resources/actions (list vs read vs send vs search vs edit). The only mild overlaps are slack_read_channel vs slack_read_thread and slack_open_dm vs slack_send_message, but descriptions clearly differentiate them (history vs thread replies, and opening vs sending).
All tools use a consistent slack_ prefix and follow verb_noun ordering (list_conversations, read_channel, send_message). The only minor deviation is slack_auth_test, where the noun/verb order is inverted, but it remains readable.
Eleven tools is well within the 3-15 sweet spot for a Slack messaging surface. Each tool covers a distinct operation (auth, list, read, search, send, edit, react, permalink, open DM) without redundancy.
Core read/write workflows (list, read, search, send, edit, react, permalink, open DM) are covered. Minor gaps remain: no delete/remove message, no documented way to send a thread reply (thread_ts not exposed), and no file upload support.