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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_messageB | Post a Slack message via Incoming Webhook. |
| send_payloadA | Post a pre-built Slack webhook payload (object or array of objects). Same contract as send_to_slack.sh: a single payload object, or an array for multi-part messages (1s spacing between parts, 429 retry). |
| send_markdownA | Convert Markdown to Slack Block Kit and send via Incoming Webhook. Handles headings, dividers, code blocks, tables (bullets when links are present), mrkdwn inline formatting, Slack size limits, and multi-part splitting with (n/m) sequence headers. |
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 3 tools
The three tools are all variations of sending messages to Slack, which creates some overlap. send_payload and send_message especially could be confused, though send_markdown is clearly distinct. The descriptions help clarify input format differences, but the boundaries are not fully crisp.
All tool names follow a consistent send_verb_noun pattern: send_payload, send_markdown, send_message. This makes the set predictable and easy to navigate.
With only 3 tools, the server is tightly scoped to its purpose of sending Slack messages via webhook. Each tool covers a distinct input format, and there are no redundant or unnecessary tools.
For the stated domain of sending Slack messages via incoming webhooks, the server covers all major input formats: raw payload, markdown, and plain message. There are no obvious gaps for this narrow scope, though full Slack API features like reading messages are intentionally excluded.