Slack MCP Server
Related Servers
Alternatives to Slack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server implementation that enables AI assistants to interact with Slack workspaces, allowing them to browse channels, send messages, reply to threads, add reactions, and retrieve user information.965 npm2Apache 2.0
- 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.1MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with Slack API, allowing users to send messages, view channel history, manage channels, send direct messages, and retrieve user lists from Slack workspaces.1-
- AlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol server for Slack integration that enables messaging, channel management, and workspace search capabilities.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Slack integration, allowing Claude to interact with your Slack workspace.53,213 npmMIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to interact with Slack workspaces through OAuth 2.0 authentication. It provides tools for listing channels and posting messages while supporting secure token persistence and dynamic client registration.-
TDQS
Scored across 11 tools
Most tools target distinct actions (post, reply, react, list, search), and the history-vs-search-messages pair is explicitly disambiguated in the descriptions. The main overlap is slack_get_users (all users, basic info) versus slack_get_user_profiles (bulk profile info) versus slack_search_users, where the boundary between the first two is unclear.
All tools use a uniform slack_<verb>_<noun> snake_case convention (slack_post_message, slack_list_channels, slack_search_users), with verbs chosen sensibly for the action. No mixed casing or inconsistent prefixes.
Eleven tools is well within a reasonable range for a Slack integration and each tool maps to a recognizable Slack operation. Nothing feels padded or missing at the count level.
Core read/write workflows (post, reply, react, read history/threads, search, list channels/users) are covered, but the message lifecycle is incomplete: no update_message, delete_message, or remove_reaction, and there is no direct-message or channel-management (create/join) coverage. These are notable gaps that would force agents into dead ends for common Slack tasks.