🧪 Community ✓ Claude Code ✓ Claude Desktop 🔌 Requires MCP Server • Rootly

Rootly

Rootly - incident management, postmortems, SRE automation

🔌 Recommended MCP Server

Pair this plugin with the Rootly MCP for direct API access alongside skills and commands.

Installation

Install this plugin individually:

/plugin marketplace add wyre-technology/msp-claude-plugins --plugin rootly

Or install all MSP plugins at once:

/plugin marketplace add wyre-technology/msp-claude-plugins

Features

Alert Handling
Incident Management
On-Call Scheduling
Postmortems
Services
Workflows

Skills

This plugin provides 7 skills that teach Claude about Rootly:

Skill	Description
`alerts`	Rootly's alerting layer between monitoring tools and incident management: alert sources (`alerts_source`) and their webhook/email intake, alert routing rules, alert groups (deduplication/noise reduction), alert urgencies, escalation policies, and the acknowledge/resolve actions on an individual alert.
`incidents`	Incidents, Rootly's primary resource: the incident lifecycle and status transitions, severity levels, the incident field reference, AI-assisted analysis via find_related_incidents and suggest_solutions, action items, alert attachment, and cross-vendor PSA ticket correlation.
`oncall`	Rootly on-call visibility built on the get_oncall_handoff_summary, get_oncall_shift_metrics, get_shift_incidents, get_oncall_schedule_summary and check_responder_availability tools: schedule and rotation coverage, structured shift handoffs, per-shift incident scoping, shift metric fields, and the burnout risk signals.
`postmortems`	Rootly postmortems as structured post-incident retrospectives: Rootly's retrospective process/step model (there is no standalone "postmortem" object), per-step status tracking through to completion, action item creation and tracking, and the blameless review practices Rootly's model assumes.
`services`	The Rootly service catalog: the real service record (ownership via owner teams/users, Slack channels, dependency modeling via linked service IDs, and third-party links to PagerDuty/Opsgenie/Cortex/Backstage/GitHub/GitLab), service CRUD, incident/uptime charts per service, and how services link back to incidents and alerts.
`workflows`	Rootly's incident-response automation model: workflow tasks (each with a concrete `task_type` like `create_slack_channel` or `page_rootly_on_call_responders`), the trigger-type/`triggers`-event structure (incident, post_mortem, action_item, alert, pulse, simple), the ID-list based condition/matching fields, and the `enabled` flag used to turn a workflow on or off (there is no separate enable/disable tool).
`api-patterns`	The Rootly hosted MCP server and the JSON:API REST surface behind it: Global vs. Team token types and how the gateway injects credentials, the catalog of roughly 253 dynamically generated tools by category, page-number pagination and relationship includes, filter syntax, rate limits, and error handling.

Agents

This plugin provides 2 agents for autonomous task execution:

Agent	Description
`incident-commander`	Use this agent when an MSP engineer, SRE, or incident manager needs to command an active Rootly incident or review open incidents.
`post-mortem-writer`	Use this agent when an MSP engineer, SRE, or incident manager needs to generate a structured post-incident review (PIR) for a resolved Rootly incident — not live incident command, but a thorough retrospective document covering what happened, why it happened, the full impact timeline, contributing factors, and the concrete action items the team is committing to fix.

Commands

Available slash commands:

Command	Description
`/action-items`	List outstanding action items from Rootly postmortems and incidents
`/create-incident`	Create a new incident in Rootly with title, severity, and affected services
`/incident-triage`	Triage active Rootly incidents by severity and status
`/postmortem-summary`	Generate a postmortem summary for a resolved Rootly incident
`/service-status`	Check service health and dependency status across the Rootly service catalog

API Reference

Base URL
Authentication
Rate Limit
Documentation

Example Usage

List outstanding action items from Rootly postmortems and incidents

/action-items

Create a new incident in Rootly with title, severity, and affected services

/create-incident

Triage active Rootly incidents by severity and status

/incident-triage

Generate a postmortem summary for a resolved Rootly incident

/postmortem-summary

Check service health and dependency status across the Rootly service catalog

/service-status

Using Skills

/skill rootly:alerts

Rootly's alerting layer between monitoring tools and incident management: alert sources (`alerts_source`) and their webhook/email intake, alert routing rules, alert groups (deduplication/noise reduction), alert urgencies, escalation policies, and the acknowledge/resolve actions on an individual alert.