Slack MCP Server
Related Servers
Alternatives to Slack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to search and retrieve messages within a Slack workspace using the Slack Web API. It supports specific channel filtering and includes built-in rate limit handling for efficient message discovery.56 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Slack workspaces through tools for managing channels, sending messages, and retrieving user profiles. It leverages the Slack API and FastMCP to provide functionalities like message history lookup and reaction management.1-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables LLMs to access Slack's search functionality to retrieve users, channels, messages, and thread replies from a Slack workspace.4-
- AlicenseNot gradedqualityBmaintenanceA production-ready MCP server for the Slack API that enables searching, listing channels, reading history, inspecting users, fetching threads, and sending messages through controlled Slack tools.30,839 npmMIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides integration with the Slack API via HTTP transport, allowing for channel management and message operations. It enables users to list channels, send or edit messages, search message history, and retrieve user information through standardized tools.56 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP 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.1MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_channel_history retrieves messages from a specific channel, list_channels enumerates available channels, and search_messages performs cross-channel searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (get_channel_history, list_channels, search_messages), using snake_case uniformly. The verbs (get, list, search) are appropriate and predictable, enhancing readability and usability.
With only 3 tools, the server feels thin for a Slack integration, as it lacks essential operations like sending messages, managing users, or handling reactions. While the tools are well-defined, the count is borderline low for the domain's typical scope.
The toolset is significantly incomplete for a Slack server, missing core CRUD operations such as sending messages, creating channels, updating messages, or deleting content. This creates dead ends for agents trying to perform common Slack workflows, likely leading to failures.