Use Rootly inside Cursor for incident response, on-call, status updates, handoffs, retrospectives, and deploy checks.
This plugin brings Rootly context directly into Cursor so you can investigate incidents, understand on-call coverage, draft communications, and prepare follow-up artifacts without constantly switching between tools. It is designed to be command-first, with clean workflows for the tasks teams repeat most during production response.
Use it when you want to:
- validate Rootly connectivity from Cursor
- investigate an incident with live Rootly context
- check current on-call ownership and upcoming handoffs
- draft status updates, briefs, handoffs, and retrospectives
- sanity-check deploy risk against active incidents and responder coverage
The main user-facing interface is the Rootly command set. Start with /rootly-setup, then use the other commands as focused workflows for the job at hand.
- Install Rootly from the Cursor marketplace, or add this repository as a plugin source.
- Create a Rootly API token in Rootly > Settings > API Keys.
- Make sure
ROOTLY_API_TOKENis available in the environment Cursor launches with. - Restart Cursor if needed.
- Run
/rootly-setup.
Example:
export ROOTLY_API_TOKEN=your_token_hereCursor must be launched after the variable is set so the app can inherit it.
/rootly-setup verifies:
ROOTLY_API_TOKEN- Rootly MCP connectivity
- a lightweight tool call
The simplest way to use the plugin is through the /rootly-* commands below. In practice, most teams start with:
/rootly-incident <id>during active response/rootly-oncallfor ownership and handoff context/rootly-status <id>for updates/rootly-retro <id>after resolution
/rootly-setup- validate auth and Rootly connectivity/rootly-incident- investigate an incident and produce a response brief/rootly-oncall- show current on-call, next handoff, and shift health/rootly-status- draft an internal, leadership, or customer-facing status update/rootly-brief- generate a concise stakeholder brief/rootly-handoff- prepare an incident or on-call handoff/rootly-retro- draft a markdown retrospective/rootly-deploy-check- review deploy risk using Rootly context
/rootly-setup/rootly-incident 4187/rootly-status 4187/rootly-handoff/rootly-retro 4199/rootly-deploy-check
