slack-cc

What it does

We built this because it didn't exist. Claude Code sessions are stuck in the terminal — no way to talk to them from the couch, no way to approve a tool call from your phone, no way to get a notification when the agent needs you. slack-cc fixes that with a Slack app that speaks MCP.

Socket Mode means no public URL, no deployment, no exposed endpoints. The MCP server spawns locally alongside Claude Code and keeps an outbound WebSocket open to Slack. Works behind firewalls, NAT, anywhere.

Key features

• Four Slack tools — reply, react, edit_message, fetch_messages — Claude drives the conversation
• Permission relay — approval prompts mirror to Slack; reply yes/no from your phone
• Auto-opt-in channels — @mention the bot, channel connects for that session
• Session-scoped security — @mentioned channels die when the session ends
• Sender gating — unknown senders dropped before reaching Claude
• Debug MCP — 12 diagnostic tools across 7 layers (tokens, permissions, API, channels, process, server, config)
• Token lockdown — .env is 0600, never logged, never in tool results

Install

git clone https://github.com/eidos-agi/slack-cc ~/repos/slack-cc
cd ~/repos/slack-cc && npm install

claude --plugin-dir ~/repos/slack-cc \
       --dangerously-load-development-channels server:slack

Usage

# In the Claude Code session — configure tokens
/slack-cc:configure xoxb-your-bot-token xapp-your-app-token

# DM the bot in Slack to pair, then:
/slack-cc:access pair <code>

# Or @mention the bot in any channel — auto-connects for the session

# Permanent channel opt-in
/slack-cc:access channel C0AV895UKFS

MIT. 108 tests across 23 suites. Full diagnostics in DIAGNOSTICS.md.

What's next

slack-cc is step one — a bridge to a Claude Code session. Step two is Slack for Eidos: not a bridge, an identity. Eidos in your workspace as a teammate with its own presence, history, and handle. Coming soon.