smithery-ai-slack
Server Details
Enable interaction with Slack workspaces. Supports subscribing to Slack events through Resources.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 37 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- smithery-ai/mcp-servers
- GitHub Stars
- 95
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose targeting specific Slack operations: message posting, reaction management, channel listing, user/profile retrieval, and message history/thread access. No ambiguity exists as tools like slack_get_channel_history and slack_get_thread_replies serve different message contexts, while slack_get_user_profile and slack_get_users handle individual vs. collective user data.
All tools follow a consistent snake_case pattern with the prefix 'slack_' followed by a verb_noun structure (e.g., slack_post_message, slack_get_users). This predictability makes it easy for agents to understand and select tools without confusion from mixed conventions.
With 7 tools, this server is well-scoped for Slack interactions, covering core messaging, user management, and channel operations. Each tool earns its place by addressing a distinct aspect of the domain, avoiding bloat while providing essential functionality for typical agent workflows.
The toolset covers key Slack operations like posting messages, retrieving data, and managing reactions, but lacks update/delete capabilities for messages or channels. Agents can work around this by reposting or using other methods, but the absence of tools like slack_update_message or slack_delete_message creates minor gaps in lifecycle coverage.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
7 tool updates
- First observed
slack_add_reaction - First observed
slack_get_channel_history - First observed
slack_get_thread_replies - First observed
slack_get_user_profile - First observed
slack_get_users - First observed
slack_list_channels - First observed
slack_post_message
Related MCP Connectors
Central Slack/Telegram router with jobs, memory, approvals, and A2A delegation
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to interact with Slack through Web API tools and subscribe to inbound Slack messages via Socket Mode notifications.11 npm2MIT
- AlicenseBqualityDmaintenanceEnables interaction with Slack workspaces to manage channels, post messages, add reactions, view message history and threads, and retrieve user profiles through the Model Context Protocol.88 npmISC
- AlicenseAqualityCmaintenanceEnables interaction with Slack workspaces as a user, supporting channel listing, message posting, threading, reactions, and user management via the Slack API.811MIT
- FlicenseAqualityBmaintenanceEnables interaction with Slack channels including checking Xcode Cloud build status, reading and searching messages, sending messages, and listing channels.51-
Glama MCP Gateway
Add one secure layer between your agents and this server.