Rootly MCP
Wire Claude or Cursor to Rootly so your agent can list, update, and reason over incidents, alerts, and on-call schedules without leaving the chat.
Overview
Rootly MCP is a MCP server for the Operate phase that exposes Rootly incidents, alerts, and on-call data to your agent via typed commands and a local SQLite mirror.
What is this MCP server?
- Typed MCP commands over every Rootly incident, alert, and on-call object
- Local SQLite mirror for faster queries and offline-style lookups from the agent
- stdio MCP transport (mcpb package v0.1.0)
- Requires ROOTLY_API_KEY and ROOTLY_API_TOKEN environment credentials
- Servosity msp-skills repo skill under skills/rootly
- Server version 0.1.0
- Transport: stdio
- Package registryType: mcpb
Community signal: 1 GitHub stars.
What problem does it solve?
During an outage you waste minutes tab-hopping between Rootly and your IDE while the agent cannot see live incident or on-call context.
Who is it for?
Indie operators or tiny teams already on Rootly who want agent-driven incident lookups and on-call awareness during production work.
Skip if: Builders with no Rootly subscription or those still in idea-only phase with no on-call process.
What do I get? / Deliverables
After install, your agent can query and act on Rootly objects from the same session where you debug and deploy fixes.
- Agent-callable Rootly incident, alert, and on-call operations
- Local SQLite-backed mirror for repeated agent queries
Recommended MCP Servers
Journey fit
How it compares
MCP integration to Rootly’s API, not a standalone incident-runbook skill or generic PagerDuty replacement.
Common Questions / FAQ
Who is Rootly MCP for?
Solo builders and small teams using Rootly for incidents and on-call who want Claude Code, Cursor, or Codex to read and drive Rootly data through MCP.
When should I use Rootly MCP?
Use it in Operate when you run production services on Rootly and need your agent to inspect incidents, alerts, or schedules while you triage or write comms.
How do I add Rootly MCP to my agent?
Install the mcpb release (rootly-v0.1.0), set ROOTLY_API_KEY and ROOTLY_API_TOKEN, register the stdio server in your MCP client config, and restart the agent.