Rootly
Triage incidents, alerts, and Rootly workflows from your agent when production breaks or pages fire.
Overview
com.mcparmory/rootly is a MCP server for the Operate phase that manages Rootly incident alerts, events, and automations from your coding agent.
What is this MCP server?
- MCP integration for Rootly incident alerts, events, and workflow automation
- Lets agents query and act on incident context alongside logs and deploy notes
- Version 1.0.5 with mcparmory-rootly on PyPI (uvx) and ghcr.io/mcparmory/rootly:1.0.5 Docker
- Stdio MCP transport from MCP Armory registry metadata
- Supports solo on-call builders who use Rootly but live in the IDE during fires
- Server version 1.0.5
- 2 packages: PyPI mcparmory-rootly and OCI Docker image
- stdio transport; source repository github.com/mcparmory/registry
Community signal: 25 GitHub stars.
What problem does it solve?
During an outage you bounce between Rootly, Slack, and the IDE while the agent lacks structured incident and alert context.
Who is it for?
Small teams on Rootly for incident management who want agent-assisted triage, event lookup, and automation triggers while debugging.
Skip if: Pre-launch projects with no on-call stack, or orgs using PagerDuty-only workflows without Rootly.
What do I get? / Deliverables
After setup, the agent can interact with Rootly via MCP so incident updates and workflow steps stay coordinated with your fix in one session.
- Rootly MCP tools available to the agent during incidents
- Faster correlation between codebase fixes and Rootly event/workflow updates
- Agent-readable incident context without leaving the dev environment
Recommended MCP Servers
Journey fit
How it compares
MCP hook into Rootly incident tooling, not a log aggregator skill or generic runbook markdown pack.
Common Questions / FAQ
Who is com.mcparmory/rootly for?
Builders and lean teams using Rootly for incidents who want MCP-aware agents to read alerts, events, and workflows during production issues.
When should I use com.mcparmory/rootly?
In Operate when pages fire or postmortems need data—you register it so the agent can work Rootly alongside code changes and deploy checks.
How do I add com.mcparmory/rootly to my agent?
Add stdio MCP config for uvx mcparmory-rootly 1.0.5 or the published Docker image and provide Rootly API credentials according to MCP Armory and Rootly docs.