Slack

Team communication hub for Databayt. Connected to Claude Code via MCP for notifications, dispatch, and collaboration.

Workspace

Share the invite link with team members to join.

Channels

Recommended channel structure:

MCP Integration

Slack MCP is configured in .claude/mcp.json:

Copy"slack": {
  "type": "http",
  "url": "https://mcp.slack.com",
  "env": {
    "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
    "SLACK_WORKSPACE_ID": "${SLACK_WORKSPACE_ID}"
  }
}

Setup Steps

1. Create Slack App

1. Go to api.slack.com/apps
2. Click Create New App > From scratch
3. Name: Kun Bot (or Databayt Bot)
4. Workspace: hogwarts-wve9301

2. Configure Bot Scopes

Under OAuth & Permissions > Bot Token Scopes, add:

3. Install App to Workspace

1. Under Install App, click Install to Workspace
2. Authorize the requested permissions
3. Copy the Bot User OAuth Token (starts with xoxb-)

4. Get Workspace ID

Find your Workspace ID:

Copy# Option 1: From Slack URL
# Open Slack in browser, workspace ID is in the URL:
# https://app.slack.com/client/T_WORKSPACE_ID/...
 
# Option 2: From Slack API
curl -s -H "Authorization: Bearer xoxb-YOUR-TOKEN" \
  https://slack.com/api/auth.test | jq '.team_id'

5. Set Environment Variables

Add to your .env file:

CopySLACK_BOT_TOKEN=xoxb-your-bot-token
SLACK_WORKSPACE_ID=T_your_workspace_id

Or export in shell:

Copyexport SLACK_BOT_TOKEN="xoxb-your-bot-token"
export SLACK_WORKSPACE_ID="T_your_workspace_id"

6. Store in Keychain (Recommended)

Copy# Store securely in macOS Keychain
security add-generic-password -a "slack" -s "SLACK_BOT_TOKEN" -w "xoxb-your-token" -U
security add-generic-password -a "slack" -s "SLACK_WORKSPACE_ID" -w "T_your_id" -U

7. Verify Connection

After setting credentials, restart Claude Code and test:

Copy# Say "slack" to trigger the MCP
# Or use directly:
claude "list slack channels"

Usage in Claude Code

Once connected, the slack keyword triggers the MCP:

From Agents

Agents like captain, ops, and support can use Slack for:

• Captain: Weekly dispatches to #dispatch
• Ops: Deploy notifications to #ops, incident alerts to #alerts
• Support: Customer issue updates to #hogwarts
• Growth: Content announcements to #general

Dispatch Integration

The dispatch system can route messages through Slack:

Copy# Captain dispatch goes to both Apple Notes and Slack
dispatch slack "Weekly: revenue at $X, 3 PRs merged, hogwarts demo Thursday"

Cowork Bridge

Slack complements the Cowork / Claude Code bridge:

Non-technical team members (Samia, Sedon) use Slack directly instead of Claude Code.

GitHub Integration

Kun bridges Slack and GitHub — team members describe issues in Slack, kun creates them in GitHub and posts the link back.

Workflow

Team member in Slack → describes bug/feature
       ↓
Claude Code reads Slack (Slack MCP)
       ↓
Creates GitHub issue (GitHub MCP)
       ↓
Posts issue link back to Slack

Usage

Example

In #dev, Ali posts: "Login page crashes on Safari mobile when switching to Arabic"

Copy# Claude Code creates the issue
gh issue create --repo databayt/hogwarts \
  --title "Login crashes on Safari mobile (Arabic/RTL)" \
  --body "Reported by Ali in #dev. Login page crashes on Safari mobile when switching to Arabic."
 
# Posts back to #dev
"Created databayt/hogwarts#15 — assigned to abdout"

Channel → Repo Mapping

Two-Way Sync

GitHub activity flows back to Slack:

Security Notes

• Bot tokens start with xoxb- — never commit to git
• Store in macOS Keychain or .env (gitignored)
• Rotate tokens if compromised at api.slack.com/apps
• Limit bot scopes to what's actually needed
• The bot can only access channels it's been invited to