MCP Server for Slack
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_TEAM_ID | Yes | Your Slack Team ID | |
| SLACK_BOT_TOKEN | Yes | Your Slack Bot User OAuth Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slack_list_channelsB | List public channels in the workspace with pagination |
| slack_post_messageB | Post a new message to a Slack channel |
| slack_reply_to_threadB | Reply to a specific message thread in Slack |
| slack_add_reactionB | Add a reaction emoji to a message |
| slack_get_channel_historyC | Get recent messages from a channel |
| slack_get_thread_repliesB | Get all replies in a message thread |
| slack_get_usersB | Get a list of all users in the workspace with their basic profile information |
| slack_get_user_profileB | Get detailed profile information for a specific user |
| lookup_user_by_emailC | Lookup a user by their email address |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, lookup_user_by_email targets user identification, slack_get_channel_history retrieves channel messages, and slack_post_message handles message creation, ensuring agents can easily differentiate between them.
The naming is mostly consistent with a 'slack_' prefix and descriptive verb_noun patterns, but there is one deviation: lookup_user_by_email lacks the 'slack_' prefix, which slightly breaks the pattern while remaining readable.
With 9 tools, the count is well-scoped for a Slack integration server. It covers core functionalities like user management, messaging, and channel operations without being excessive or insufficient for the domain.
The tool set provides comprehensive coverage for common Slack workflows, including user lookup, messaging, and channel interactions. A minor gap exists in lacking tools for updating or deleting messages, but agents can still perform most essential tasks effectively.