/discord-ops — Discord ChatOps Reference

This skill documents the Discord ChatOps integration that lets you control Claude Code from Discord.

Architecture

Discord #claude-ops → Bot listener (local Mac) → claude -p "<command>" → Result → Discord reply

The Discord MCP server (~/discord-mcp/) runs a chatops listener alongside the MCP tools. Commands typed in #claude-ops by authorized users are validated, then executed via Claude Code CLI.

Channels

Channel	Purpose
#deployments	Automated CI/CD notifications (webhook)
#claude-ops	ChatOps commands — type here to control Claude Code
#general	Manual posts (PR summaries, status updates)

Available Commands (from Discord)

CI Failure Remediation

Command	What it does
fix ci	Analyze latest CI failure, apply fixes, commit & push
ci status	Check latest CI run status (pass/fail)
ci logs	Get failure logs from latest failed CI run
ruff fix	Auto-fix lint errors in backend + agent
fix types	Check and report TypeScript errors
fix tests	Run failing tests and report what broke
migration check	Validate alembic migrations (heads, numbering)

CI Fix Flow (from phone/Discord)

1. Get Discord alert in #deployments: "CI failed on branch X"
2. Go to #claude-ops
3. Type: ci logs          → see what failed
4. Type: fix ci           → Claude reads logs, fixes, commits, pushes
5. Type: ci status        → verify new CI run is passing

SRE / Production

Command	What it does
/sre	Full SRE agent for production debugging
check prod health	Hit production health endpoints
check staging health	Hit staging health endpoints
deploy status	Check Railway deployment status

QA & Testing

Command	What it does
/qa	Run QA checks (commit mode)
run tests	Run backend pytest + frontend jest
run lint	Run linters without fixing

Info (read-only)

Command	What it does
git status	Show branch, changes, recent commits
pr status	List open PRs
share latest prs	Post PR summaries to Discord
show/find/search/explain ...	Any read-only codebase query

Ops

Command	What it does
/restart	Restart local dev servers
/pr	Create PR (runs QA first) — dangerous, use carefully

Blocked Commands

These patterns are always rejected for safety:

• rm -rf, sudo, git reset --hard, git push --force
• DROP TABLE, DELETE FROM
• railway up (caused Feb 13 outage)
• pip uninstall, npm uninstall
• Anything containing password, secret, token, api key

Security

• Authorized users only: Only Discord user IDs in .env can execute commands
• Channel-locked: Only messages in #claude-ops are processed
• Allowlist-based: Commands must match a known pattern — arbitrary commands rejected
• 5-minute timeout: Long-running commands are killed after 5 minutes
• Output truncated: Results capped at 1900 chars to fit Discord limits

Setup

The Discord MCP server at ~/discord-mcp/ must be running with chatops enabled:

# Required env vars in ~/discord-mcp/.env:
DISCORD_TOKEN=<bot token>
DISCORD_AUTHORIZED_USER_IDS=<comma-separated user IDs>
DISCORD_OPS_CHANNEL=claude-ops
CLAUDE_WORKING_DIR=/Users/pganapathy80/prepme
CLAUDE_PATH=claude

To add a new authorized user:

1. Get their Discord user ID (Developer Mode → right-click user → Copy User ID)
2. Add to DISCORD_AUTHORIZED_USER_IDS in ~/discord-mcp/.env (comma-separated)
3. Restart the Discord MCP server

Restarting the Discord MCP Server

# Kill existing process
pkill -f "discord-mcp/build/index.js"

# Restart
cd ~/discord-mcp && node build/index.js

Note: The MCP server runs in a terminal. Claude Code connects to it via stdio. Restarting it will require reconnecting Claude Code.