315 Claude Code plugins · 382 MCP servers · refreshed 26 Oct 2026Get your plugin featured →

rootly

Full-lifecycle incident management: deploy safety, incident response, on-call management, and retrospectives.

plugin★ 1updated 20 May 2026by Rootly
paste into Claude Code
/plugin install rootly@claude-plugins-official

How to start

  1. Paste the command into Claude Code and press Enter.
  2. Restart Claude Code so the plugin loads.
  3. Just ask Claude. Its skills step in when your request fits.

What it adds

3 agents · 18 skills · 2 hooks · 1 MCP server

Agents Claude hands work to these

  • deploy-guardianDeployment safety specialist for blast-radius analysis, downstream dependency checks, and cross-team coordination planning.
  • incident-investigatorDeep production-incident investigator for root-cause analysis, evidence gathering, and remediation planning beyond the initial response brief.
  • retro-analystReliability pattern analyst for retrospectives, recurring-incident clustering, and systemic improvement recommendations.

Skills Claude loads these when the task fits

  • actionManage incident action items from the terminal. Subcommands - list (default - your open action items) or add <incident> "<summary>" (create one on an incident)…
  • alertTriage a Rootly alert by short ID. Pulls the alert record, its event timeline, related alerts in the same group, and any incident the alert is attached to. Use…
  • announceDraft a stakeholder-facing status update for an active incident, then post it after explicit confirmation. Useful for incident commanders pushing public-status…
  • askAsk natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured…
  • briefGenerate a concise stakeholder brief for an incident. Creates executive summary with key details, impact, timeline, and current status.
  • coverOffer to cover someone else's on-call shift. Lists upcoming shifts on a team or schedule and creates an override placing you on the chosen one after explicit c…
  • deploy-check[experimental] Evaluate deployment risk by analyzing code changes against incident history, active incidents, and on-call readiness. Forked-subagent flow may n…
  • handoffPrepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.
  • lookupLook up a service, team, or catalog entity in Rootly. Returns owner, on-call, recent reliability, dependencies, and any active incidents. Use when something br…
  • myPersonal Rootly dashboard. Shows your open action items, your active incidents (where you're a responder), and your upcoming on-call shifts. Use to start the d…
  • oncallShow current on-call status, shift metrics, and health indicators for your team. Use to check who's on-call, handoff context, or on-call workload.
  • respond[experimental] Investigate and respond to a production incident. Pulls context, finds similar past incidents, suggests solutions, and enables coordination. For…
  • …and 6 more in the source.

Hooks Run on their own at these moments

  • SessionStartWhen a session starts.
  • PreToolUseBefore Claude uses a tool.

MCP servers Connections it sets up for you

  • rootlyRemote server at mcp.rootly.com

Read from the plugin's own files in Rootly-AI-Labs/rootly-claude-plugin, 26 Oct 2026.

What it needs

No keys or settings: its files ask for none. A remote server may still ask you to sign in the first time.