Rootly

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.

Service Health Check

> /rootly:status

Quick overview of all services with active incidents grouped by severity and age.

Stakeholder Communication

> /rootly:brief INC-4521

Generate executive-friendly incident summaries with impact, timeline, and current status for stakeholder updates.

Shift Handoffs

> /rootly:handoff

Create structured handoff documents for incident commanders or on-call transitions with context and next steps.

Ask Questions

> /rootly:ask "incidents this week"

Natural language queries about your incident data, on-call schedules, and service reliability patterns.

After the Dust Settles

> /rootly:retro INC-4521

Generates structured retrospectives from incident data: timeline, contributing factors, action items, and systemic patterns.

Installation

You can use this plugin in two ways:

• Marketplace install for a persistent Claude Code installation
• Local --plugin-dir loading for development and evaluation from source

Marketplace Install

This repository includes .claude-plugin/marketplace.json, so Claude Code can use the repo itself as a marketplace source.

1. Add the marketplace:

/plugin marketplace add Rootly-AI-Labs/rootly-claude-plugin

1. Open the plugin manager:

/plugin

1. In the Discover tab, select rootly and install it to your preferred scope:

• User: available across all your projects
• Project: shared through this repository's .claude/settings.json
• Local: only for you in this repository

1. Reload plugins so the install takes effect immediately:

/reload-plugins

1. Run setup -- Claude will automatically handle OAuth2 login when it connects to the MCP server:

/rootly:setup

A browser window will open for you to log in to Rootly and grant access. No API token needed.

Local Source Loading

Step 1: Clone the Plugin

git clone https://github.com/Rootly-AI-Labs/rootly-claude-plugin.git
cd rootly-claude-plugin

Step 2: Load It in Claude Code

claude --plugin-dir .

Claude Code loads the plugin directly from this directory for the current session. This is the recommended flow for local development and evaluation. For a persistent install, use the marketplace flow above.

Step 3: Verify

/rootly:setup

Direct MCP Access

This repository is a Claude Code plugin. If you only want direct Rootly MCP access in Claude Desktop / Cowork, configure the MCP server separately:

{
  "mcpServers": {
    "rootly": {
      "url": "https://mcp.rootly.com/mcp"
    }
  }
}

Claude will handle OAuth2 login automatically -- a browser window opens for you to authenticate with Rootly. No API token needed.

Setup & Configuration

After installation, run the setup command:

> /rootly:setup

First-time plugin setup with API token validation, service mapping, and quick-start guide.

Authentication

OAuth2 (Recommended)

MCP commands use OAuth2 automatically. When Claude connects to the Rootly MCP server, it handles the OAuth2 flow -- a browser window opens for you to log in and grant access. No configuration needed.

To re-authenticate, disconnect and reconnect the MCP server via /mcp.

API Token (Hook Scripts)

Hook scripts (active-incident warnings on commit/push) still use API tokens since they run outside the MCP context:

# Via plugin config (persistent)
# Set ROOTLY_API_TOKEN in the plugin's userConfig prompt

# Via env var (session-scoped)
export ROOTLY_API_TOKEN="your-token-here"

Get a token from your Rootly dashboard under Settings > API Keys.

Commands

Stable (inline, MCP-native)

Experimental (forked subagent — may not have MCP access in all contexts)

The experimental skills delegate to forked subagents. In some Claude Code contexts the subagent doesn't inherit the plugin's MCP server; when that happens it stops and reports rather than falling back to bash/curl (which would leak the API token). For reliable coverage of those workflows, prefer /rootly:brief, /rootly:status, and the inline alternatives above.

Natural Language Queries

/rootly:ask how many SEV-1 incidents did we have last month?
/rootly:ask which service has the most incidents this quarter?
/rootly:ask who's been on-call the most in the last 30 days?

Deep Investigation Agents

When a slash command isn't enough, Claude automatically invokes specialized agents for deeper analysis:

Automatic Hooks

Two lightweight hooks run in the background -- they never block your workflow:

Service Mapping

Map your repository to Rootly services by creating .claude/rootly-config.json:

{
  "services": ["auth-service", "auth-worker"],
  "team": "platform-team"
}

/rootly:setup walks you through creating this. Without it, the plugin falls back to matching your git repo name against Rootly service names.

Advanced

export ROOTLY_API_URL="https://rootly.internal.example.com"

This overrides the REST API base URL used by hook scripts. Configure the MCP endpoint separately in .mcp.json.

Replace the HTTP transport in .mcp.json:

{
  "mcpServers": {
    "rootly": {
      "command": "uvx",
      "args": ["--from", "rootly-mcp-server", "rootly-mcp-server"],
      "env": {
        "ROOTLY_API_TOKEN": "${user_config.ROOTLY_API_TOKEN}"
      }
    }
  }
}

claude mcp add rootly --transport http https://mcp.rootly.com/mcp

OAuth2 login will be triggered automatically on first use.

An optional script (scripts/register-deploy.sh) can register deployments with Rootly after git push. It is not enabled by default -- see the script header for hook configuration.

Troubleshooting

Architecture

See ARCHITECTURE.md for the full technical design: MCP integration, hook system, agent orchestration, and data flow.

License

Apache 2.0 -- see LICENSE.

…