Rootly for Claude Code
Incident management meets AI-powered development.
Prevent, respond, and learn from incidents -- without leaving your terminal.
Why
You're in the zone writing code. Then:
- You
git push and realize there's a SEV-1 in progress
- You get paged and scramble between Slack, Datadog, and your incident tool
- The retro after an incident takes hours to compile
This plugin brings Rootly's incident lifecycle into Claude Code -- so you can assess deployment risk, investigate incidents, check on-call, and generate retrospectives from the same terminal where you write code.
What You Get
Before You Deploy
> /rootly:deploy-check
Analyzes your git diff against past incidents. Warns you if similar changes caused outages before. Checks if on-call coverage exists.
|
When You Get Paged
> /rootly:respond INC-4521
Pulls full incident context, finds similar past incidents, suggests proven solutions, and shows who's on-call -- all in one brief.
|
During Your Shift
> /rootly:oncall
See who's on-call across all schedules, shift metrics, upcoming handoffs, and health risk indicators.
|
After the Dust Settles
> /rootly:retro INC-4521
Generates a structured retrospective from incident data: timeline, contributing factors, action items, and systemic patterns.
|
Installation
We've applied to have this plugin listed on the official Claude Code plugin marketplace. In the meantime, install manually:
Step 1: Connect the Rootly MCP Server
The plugin requires the Rootly MCP server to access incident data. You must configure it before using the plugin.
Get an API token from your Rootly dashboard under Settings > API Keys, then configure the MCP server for your platform:
Claude Code (CLI)
The plugin's .mcp.json handles this automatically. Just set the token:
# Add to your shell profile (~/.bashrc, ~/.zshrc)
export ROOTLY_API_TOKEN="your-token-here"
Or add to ~/.claude/settings.json:
{
"env": {
"ROOTLY_API_TOKEN": "your-token-here"
}
}
Claude Desktop / Cowork
Add the Rootly MCP server to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"rootly": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://mcp.rootly.com/mcp",
"--header", "Authorization:Bearer YOUR_TOKEN_HERE"
]
}
}
}
Replace YOUR_TOKEN_HERE with your Rootly API token. Restart Claude Desktop after saving.
Note: Claude Desktop requires stdio-based MCP servers. The mcp-remote package bridges the remote Rootly HTTP server into the stdio transport that Desktop expects.
Step 2: Install the Plugin
Claude Code (CLI):
git clone https://github.com/Rootly-AI-Labs/claude-rootly-plugin.git
claude --plugin-dir ./claude-rootly-plugin
Claude Desktop / Cowork: Upload rootly.zip via the Customize menu in Cowork, or browse the plugin marketplace once listed.
Step 3: Verify
/rootly:setup
Commands
| Command | What It Does |
|---|
/rootly:setup | First-run configuration and connection check |
/rootly:deploy-check | Pre-deploy risk analysis against incident history |
/rootly:respond [id] | Investigate and respond to a live incident |
/rootly:oncall [team] | On-call dashboard with shift metrics |
/rootly:retro [id] | Generate a post-incident retrospective |
/rootly:status [service] | Service health overview -- active incidents at a glance |
/rootly:ask [question] | Ask anything about your incident data in plain English |
Natural Language Queries
Rootly-AI-Labs