slack-mcp-server
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 | Slack Team ID (starts with T) | |
| SLACK_BOT_TOKEN | Yes | Slack Bot User OAuth Token (starts with xoxb-) | |
| SLACK_CHANNEL_IDS | No | Optional: Comma-separated list of predefined channel IDs |
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_messageA | Post a new message to a Slack channel or direct message to user. Accepts both channel names (#general, general) and channel IDs (C1234567890). |
| slack_reply_to_threadC | Reply to a specific message thread in Slack. Accepts both channel names (#general, general) and channel IDs (C1234567890). |
| slack_add_reactionA | Add a reaction emoji to a message. Accepts both channel names (#general, general) and channel IDs (C1234567890). |
| slack_get_channel_historyA | Get recent messages from a channel. Accepts both channel names (#general, general) and channel IDs (C1234567890). |
| slack_get_thread_repliesA | Get all replies in a message thread. Accepts both channel names (#general, general) and channel IDs (C1234567890). |
| 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 |
| slack_post_markdown_messageA | Post a new message to a Slack channel or direct message with markdown formatting enabled. Accepts both channel names (#general, general) and channel IDs (C1234567890). Supports Slack's mrkdwn formatting like bold, italic, |
| slack_reply_to_thread_markdownA | Reply to a specific message thread in Slack with markdown formatting enabled. Accepts both channel names (#general, general) and channel IDs (C1234567890). Supports Slack's mrkdwn formatting like bold, italic, |
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 10 tools
Each tool targets a distinct Slack operation: reacting, reading history, threads, user info, listing, posting, and replying. The two posting variants (plain vs markdown) are clearly differentiated, and reply tools also follow the same pattern. No ambiguity.
All tools consistently use the 'slack_' prefix followed by a clear verb_noun pattern in snake_case. Verbs like add, get, list, post, reply are used uniformly. Minor variation between 'get' and 'list' is acceptable and common.
With 10 tools, the set covers a broad but focused range of Slack interactions (message reading/writing, reactions, user and channel info) without being overwhelming or sparse. Each tool feels necessary for typical agent tasks.
Core operations are well-covered: reading channels/threads, posting messages, reacting, and retrieving user/channel info. Missing update/delete message capabilities and search, but these are not critical for common use cases, making the surface mostly complete.