Slack User MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_TOKEN | Yes | User OAuth Token that starts with xoxp- | |
| SLACK_TEAM_ID | Yes | Your Slack Team ID (starts with a T) |
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 |
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 targeting specific Slack operations: adding reactions, retrieving channel history, fetching thread replies, getting user profiles, listing users, listing channels, posting messages, and replying to threads. There is no overlap or ambiguity between these functions.
All tool names follow a consistent 'slack_verb_noun' pattern using snake_case, such as slack_post_message and slack_get_user_profile. This uniformity makes the tool set predictable and easy to navigate.
With 8 tools, the server is well-scoped for a Slack integration, covering essential messaging, user management, and channel operations. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.
The tool set provides strong coverage for core Slack workflows, including message posting, reactions, threading, and user/channel listing. Minor gaps exist, such as updating or deleting messages, but agents can likely work around these with the available tools.