Slack MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_BOT_TOKEN | Yes | Bot User OAuth Token for Slack (starts with xoxb-) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| slack_create_channelA | Create a new Slack channel (public or private) |
| slack_invite_to_channelB | Invite users to a Slack channel by email or user ID |
| slack_post_messageC | Post a message to a Slack channel. Supports markdown formatting. |
| slack_post_threadA | Reply to a message in a thread |
| slack_pin_messageB | Pin a message to a channel |
| slack_list_usersA | List all users in the Slack workspace for user ID lookup |
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 6 tools
Each tool targets a distinct action: creating channels, inviting users, listing users, pinning messages, posting messages, and replying in threads. No overlap in purpose.
All tools follow a consistent 'slack_verb_noun' pattern in snake_case, making them predictable and easy to differentiate.
With 6 tools, the set is concise and covers essential Slack operations without being overly large or sparse.
Missing critical operations like reading messages, listing channels, editing/deleting messages, and direct messaging, which limits the server's utility for typical Slack workflows.