Slack Message MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server (optional, default 3000) | |
| SLACK_BOT_TOKEN | Yes | Slack bot token (xoxb-...) | |
| SLACK_CHANNEL_ID | Yes | Slack channel ID to post messages to |
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 |
|---|---|
| post_slack_messageA | Post a message to the Slack channel configured by SLACK_CHANNEL_ID. |
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 1 tool
Only one tool exists, so there is no possibility of ambiguity or overlap with other tools.
With a single tool, naming consistency is inherent; the tool name 'post_slack_message' is clear and follows a standard verb_noun pattern.
Having only one tool for a communication platform like Slack feels insufficient; users would typically expect additional tools for reading, editing, or deleting messages.
The server is severely incomplete; it only supports posting messages to a single configured channel, lacking any retrieval, modification, or multi-channel capabilities.