SockDock for Slack
Related Servers
Alternatives to SockDock for Slack
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that connects Claude Code to Slack, allowing two-way communication via Slack Socket Mode without tunnels.1MIT
- AlicenseNot gradedqualityCmaintenanceRelays 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.30 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
- FlicenseBqualityDmaintenanceMCP server for Slack workspace integration, exposing 40+ Slack operations as tools for Claude Desktop and providing a clean async Python API.641-
- -licenseNot gradedqualityBmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm91,952MIT
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
TDQS
Scored across 13 tools
Most tools have clearly distinct purposes: rule CRUD, run control, diagnostics, user lookup, and channel listing are well separated. There is some overlap among sockdock_check_rule, sockdock_test_match, sockdock_list_rules, and sockdock_get_status because all can surface rule or connection diagnostics, but the descriptions explicitly guide when to use each.
All tool names use the same sockdock_ prefix and consistent snake_case verb_noun structure, such as sockdock_get_rule, sockdock_list_runs, and sockdock_save_rule. The pattern is predictable throughout the set.
The 13 tools are well scoped for a Slack automation rule manager, covering rule lifecycle, run monitoring, diagnostics, users, and channels. Each tool appears to earn its place without excessive fragmentation.
The surface covers rule creation, reading, updating, deletion, enabling/disabling, reordering, testing, and diagnosis, plus run listing/stopping and status checks. Supporting needs such as finding users and listing available channels are also present, leaving no obvious workflow dead ends.