Slack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_BOT_TOKEN | Yes | Your Slack Bot User OAuth Token (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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_channelsC | List channels in the Slack workspace |
| get_channel_infoC | Get detailed information about a specific channel |
| create_channelC | Create a new channel |
| archive_channelC | Archive a channel |
| list_usersC | List users in the Slack workspace |
| get_user_infoC | Get detailed information about a specific user |
| invite_to_channelC | Invite users to a channel |
| send_messageB | Send a message to a channel |
| update_messageC | Update an existing message |
| delete_messageC | Delete a message |
| get_channel_historyC | Get message history from a channel |
| search_messagesC | Search for messages across the workspace |
| send_formatted_messageB | Send a message with Block Kit formatting |
| upload_fileC | Upload a file to Slack |
| add_reactionB | Add an emoji reaction to a message |
| remove_reactionB | Remove an emoji reaction from a message |
| get_team_infoB | Get information about the Slack workspace |
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 17 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as send_message vs. send_formatted_message for different message types, and add_reaction vs. remove_reaction for opposite operations. There is no significant overlap that would cause confusion in tool selection.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions like create_channel, get_channel_history, and update_message. The naming is uniform throughout, using snake_case without any deviations or mixed conventions.
With 17 tools, the count is slightly high but reasonable for a Slack integration covering channels, messages, users, files, and reactions. It provides comprehensive functionality without being overwhelming, though it borders on the upper limit of typical scopes.
The toolset offers complete CRUD/lifecycle coverage for Slack's core domain, including channel management (create, archive, invite, list, get info), message handling (send, update, delete, search, history), user operations (list, get info), and file uploads. No obvious gaps exist for common workflows.