A
licenseNot graded
qualityB
maintenanceMCP 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.
1
MIT
slacker
Related Servers
Alternatives to slacker
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceRelays Slack direct messages into a locally running Claude Code session over MCP, so users can talk to their local agent from Slack. Replies, reactions, and execution-permission approvals (buttons or yes/no replies) are all handled inside Slack without opening ports or tunnels.5 npmMIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm91,106MIT
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
- FlicenseBqualityDmaintenanceMCP server for Slack workspace integration, exposing 40+ Slack operations as tools for Claude Desktop and providing a clean async Python API.641-
- 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
TDQS
A4/5.0
Scored across 13 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: message operations (send/edit/delete), reading (read_messages vs read_thread are cleanly separated by channel vs thread), search, discovery (list_channels, find_user, list_unread), and identity/status (whoami, get_status vs set_status). No two tools overlap ambiguously.
Naming Consistency4/5
Nearly all tools follow a clean verb_noun snake_case pattern (read_messages, send_message, edit_message, list_channels, set_status, add_reaction). The only deviation is whoami, a single-word idiom that breaks the pattern but is unambiguous and conventional.
Tool Count5/5
13 tools is well-scoped for a Slack client, covering the essential read/write/search/discovery surface without bloat. Every tool maps to a distinct capability with no filler.
Completeness4/5
Core Slack workflows are covered: reading channels/threads/DMs, sending/editing/deleting messages, reactions, search, unread tracking, user lookup, and status. Minor gaps exist around channel/fleet management (create channel, invite members, file uploads, pins), but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues