Slack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_get_usersB | Get a list of all users in the workspace with basic information |
| slack_post_messageC | Post a new message to a Slack channel |
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 2 tools
The two tools have clearly distinct purposes: one retrieves user information and the other posts messages, with no overlap in functionality. An agent can easily differentiate between them based on their descriptions.
Both tools follow a consistent 'slack_verb_noun' pattern (slack_get_users, slack_post_message), using snake_case and clear action-object naming. This makes them predictable and easy to understand.
With only 2 tools, the server feels severely under-scoped for a Slack integration, lacking essential operations like reading messages, managing channels, or handling reactions. This minimal set limits agent capabilities significantly.
The tool surface is highly incomplete for a Slack server, missing core functionalities such as reading channel messages, listing channels, updating or deleting messages, and interacting with threads. This will cause frequent agent failures in typical Slack workflows.