Slack MCP Server
Related Servers
Alternatives to Slack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm90,569MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Slack integration, allowing Claude to interact with your Slack workspace.21,724 npmMIT
- FlicenseBqualityDmaintenanceMCP server for Slack workspace integration, exposing 40+ Slack operations as tools for Claude Desktop and providing a clean async Python API.641-
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to Slack data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to interact with Slack through Web API tools and subscribe to inbound Slack messages via Socket Mode notifications.11 npm2MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves user information and the other posts messages, with no overlap in functionality. An agent can easily differentiate between them based on their descriptions.
Both tools follow a consistent 'slack_verb_noun' pattern (slack_get_users, slack_post_message), using snake_case and clear action-object naming. This makes them predictable and easy to understand.
With only 2 tools, the server feels severely under-scoped for a Slack integration, lacking essential operations like reading messages, managing channels, or handling reactions. This minimal set limits agent capabilities significantly.
The tool surface is highly incomplete for a Slack server, missing core functionalities such as reading channel messages, listing channels, updating or deleting messages, and interacting with threads. This will cause frequent agent failures in typical Slack workflows.