Claude Code Slack Channel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLACK_APP_TOKEN | Yes | App-Level Token (starts with xapp-) | |
| SLACK_BOT_TOKEN | Yes | Bot User OAuth Token (starts with xoxb-) | |
| SLACK_CHANNEL_ID | No | Optional: Channel ID to listen to only one specific channel |
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 | {} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_slack_messageA | Send a message to a Slack channel. Use this to reply to webhook channel incoming messages from Slack. |
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
With only one tool, there is no possibility of confusing it with another. The tool's purpose is also clearly stated.
The single tool uses a clear verb_noun pattern: send_slack_message. There are no other tools to create inconsistency, and the name accurately describes the action.
One tool is minimal, but it directly matches the server's narrow stated purpose of replying to Slack webhook messages. It feels slightly thin for a general Slack integration but appropriate for this specific use case.
For the stated purpose of sending Slack messages in response to incoming webhooks, the send operation covers the core need. Missing capabilities like reading messages or managing channels are not necessarily gaps if those arrive via the webhook integration.