Slack MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_MCP_PROXY | No | Proxy URL for the MCP server to use | |
| SLACK_MCP_SERVER_CA | No | Path to the CA certificate of the trust store | |
| SLACK_MCP_XOXC_TOKEN | Yes | Authentication data token field `token` from POST data field-set (`xoxc-...`) | |
| SLACK_MCP_XOXD_TOKEN | Yes | Authentication data token from cookie `d` (`xoxd-...`) | |
| SLACK_MCP_SERVER_HOST | No | Host for the MCP server to listen on | 127.0.0.1 |
| SLACK_MCP_SERVER_PORT | No | Port for the MCP server to listen on | 3001 |
| SLACK_MCP_SSE_API_KEY | No | Authorization Bearer token when `transport` is `sse` | |
| SLACK_MCP_SERVER_CA_INSECURE | No | Trust all insecure requests (NOT RECOMMENDED) | false |
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 |
|---|---|
| channels_listC | Get list of channels |
| conversations_historyB | Get messages from the channel by channel_id, the last row/column in the response is used as 'cursor' parameter for pagination if not empty |
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: channels_list retrieves a list of channels, while conversations_history fetches messages from a specific channel. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent snake_case naming convention, but the patterns differ slightly: channels_list uses a noun_verb format, while conversations_history uses a noun_noun format. This minor deviation prevents a perfect score, but the naming is still readable and mostly consistent.
With only 2 tools, this server feels too thin for a Slack integration, as it lacks essential operations like sending messages, managing users, or updating channel settings. The scope is severely limited, making it difficult for agents to perform comprehensive Slack-related tasks.
The tool surface is significantly incomplete for a Slack domain. While it covers listing channels and retrieving message history, it misses critical operations such as posting messages, creating channels, or handling reactions, which are core to Slack workflows and will likely cause agent failures.