-
licenseNot graded
qualityA
maintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.
70,822 npm
91,812
MIT
Slack MCP Server
by AVIMBU
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
- AlicenseAqualityCmaintenanceEnables AI agents such as Claude Code to read and send Slack messages as the user through a local MCP server, supporting multiple workspaces, threads, search, reactions, statuses, and dry-run/read-only safeguards.13MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for Slack integration, allowing Claude to interact with your Slack workspace.53,070 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list Slack channels, post and reply to messages, add reactions, and retrieve channel history, thread replies, users, and user profiles through the Slack Web API.MIT
- FlicenseBqualityDmaintenanceMCP server for Slack workspace integration, exposing 40+ Slack operations as tools for Claude Desktop and providing a clean async Python API.641-
TDQS
B3.1/5.0
Scored across 2 tools
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness2/5
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.