Slack Message Sender
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Log level for the MCP server (e.g., info, debug, error) | info |
| SLACK_BOT_TOKEN | Yes | Your Slack bot token (xoxb-...) with required scopes: chat:write, chat:write.public, channels:read, groups:read |
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 |
|---|---|
| send_messageB | Send a message to a Slack channel. Can be used by Claude Desktop and KADI agents to send messages to channels or start new threads. |
| send_replyA | Reply to a message in a Slack thread. Useful for maintaining conversation context. |
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 sends a new message or starts a thread, the other replies within a thread. No ambiguity.
Both tools follow a consistent 'send_' prefix and verb_noun pattern ('send_message', 'send_reply'), making the naming predictable.
With only 2 tools, the server is very focused. While this is appropriate for a minimal message sender, it feels slightly thin for general Slack interaction.
The tool set covers sending and replying, but lacks other common Slack operations (e.g., reading, editing, deleting messages), leaving notable gaps.