slack-mcp
Related Servers
Alternatives to slack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that reads Slack through your own browser session, authenticating as you rather than a bot. Provides tools to search messages, retrieve channel/DM/thread history, resolve users, and post messages (write disabled by default).10MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that gives AI agents access to your Slack workspaces using session tokens.2MIT
- AlicenseBqualityDmaintenanceThe most powerful MCP server for Slack Workspaces. This integration supports both Stdio and SSE transports, proxy settings and does not require any permissions or bots being created or approved by Workspace admins 😏.21,814MIT
- AlicenseAqualityFmaintenanceA minimal MCP server for sending Slack messages, supporting both bot and user tokens with concurrent safety and an AI bot signature in user-token mode.110 npm1MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted MCP server for Slack using User OAuth Token, enabling message management, channel operations, and user interactions via natural language.19 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for posting messages to Slack channels via webhooks or bot API. Supports configurable usernames, emojis, and both webhook and bot token authentication modes.5 npmMIT
TDQS
Scored across 18 tools
Each tool has a clearly distinct purpose: listing, searching, reading, sending (with draft/confirm), reactions, etc. No two tools appear to do the same thing; even send_message and send_reply_quote differ in threading behavior.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_channels, search_users, delete_own_message). The verbs are varied but appropriate, and there is no mixing of conventions.
At 18 tools, the server is slightly above the ideal 3-15 range but still well-scoped. Each tool has a clear role, covering workspace, channel, user, and message operations without bloat.
The tool surface covers core Slack interactions: messaging (with drafts), searching, reactions, and user profiles. Minor gaps like channel creation or file uploads exist, but the set is complete for common read/write workflows.