sethbrasile/claude-slack-channel
Platform-specific configuration:
{
"mcpServers": {
"claude-slack-channel": {
"command": "npx",
"args": [
"-y",
"claude-slack-channel"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
[](https://www.npmjs.com/package/claude-slack-channel) [](https://github.com/sethbrasile/claude-slack-channel/actions/workflows/ci.yml)
Control Claude Code from Slack. Approve dangerous tool calls without opening a terminal.
An MCP server (a tool-plugin process that Claude Code loads on startup) that bridges Claude Code sessions to a Slack channel via Socket Mode (a WebSocket connection — no public URL required). Claude receives commands from Slack, replies in threads, and posts permission prompts that operators approve or deny — all from their phone if they want to. No webhooks, no public URLs, no port forwarding.
You (Slack) Claude Code
│ │
1. │──── "deploy to staging" ───────────────▶│
│ │ runs tasks...
│ │
2. │◀── [Approve] [Deny] ────────────────────│
│ │
3. │──── clicks [Approve] ──────────────────▶│
│ │ continues...
│ │
4. │◀── "Done. Deployed to staging." ────────│
│ │---
Claude Code can run unattended — but sometimes it needs a human to approve a dangerous tool call. Without a channel server, that means sitting in front of a terminal. With claude-slack-channel, you start a job, walk away, and approve permissions from Slack when they come in.
Key differentiator: The permission relay. Other Slack bridges forward messages, but this one also relays Claude's permission requests with interactive Approve / Deny buttons so you can approve rm, git push, file writes, and other
Loading reviews...