Slack
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_TOKEN | No | Optional: Bearer token for HTTP authorization (Streamable HTTP transport only) | |
| SLACK_TEAM_ID | Yes | Your Slack Team ID (starts with a T) | |
| SLACK_BOT_TOKEN | Yes | Bot User OAuth Token that starts with xoxb- | |
| SLACK_CHANNEL_IDS | No | Optional: comma-separated list of predefined channels (e.g., 'channel1,channel2,channel3') |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slack_list_channelsB | List public and private channels that the bot is a member of, or pre-defined channels in the workspace with pagination |
| slack_post_messageB | Post a new message to a Slack channel or direct message to user |
| 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_repliesA | Get all replies in a message thread |
| slack_get_usersA | 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 |
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 8 tools
Each tool has a clearly distinct purpose: reacting, reading history, threads, user info, channels, posting, and replying. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern with a 'slack_' prefix (e.g., slack_post_message, slack_list_channels). No mixing of styles.
8 tools is well-scoped for a Slack MCP server, covering essential operations without being too many or too few.
Core CRUD for messaging and user info is covered. Minor gaps exist (e.g., editing/deleting messages, creating channels), but the surface is sufficient for typical workflow.