$ loading_
Query and manage Rootly incidents, alerts, and on-call data with a local SQLite mirror.
This Rootly MCP comes from an official registry and is open source, which improves auditability. However, it requires Rootly credentials, can execute code, and states it maintains a local SQLite mirror, so the overall posture is caution rather than high risk.
It requires ROOTLY_API_KEY and ROOTLY_API_TOKEN, both of which are sensitive credentials that can access Rootly incident, alert, and on-call objects. Misconfiguration or logging leakage could enable misuse, but the materials do not show clear signs of overbroad permission requests.
Although no remote host is listed, its stated functionality and required Rootly credentials reasonably imply communication with Rootly services and transfer of related object data. No concrete red flag is shown for exfiltration to unknown or unrelated endpoints.
The system checks explicitly indicate that this tool executes code/spawns processes, which is a common MCP capability. The available materials do not reveal extra dangerous system privileges or execution behavior unrelated to its stated purpose, so this remains a caution item.
The description states there is a 'local SQLite mirror,' indicating local persistence of Rootly-related data. This creates local data residue and access-control considerations, but the materials do not show broad reads of unrelated local files or requests for excessive permissions.
The source is an official registry entry with an auditable open-source repository and updates within the past year. While the project has low star count and no declared license, there are no high-risk supply-chain red flags such as closed source, abandonment, or suspicious distribution channels.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "Rootly MCP" yet — see the docs or source repo.
Use the Rootly MCP to fetch the current on-call schedule and list today's primary responder, backup responder, team, and handoff time.
Structured current on-call details for quickly confirming ownership and handoff timing.
Use the Rootly MCP to retrieve incidents from the last 30 days, count them by severity, and summarize frequent services and recurring issues.
An incident summary table and brief trend analysis to highlight key improvement areas.
Using the Rootly MCP local SQLite mirror, query all P1/P2 alerts and linked incidents from the last 7 days, group them by service, and find the five records with the longest response times.
Grouped results and a list of slow-response records for troubleshooting review.
Access Atera ops and service data for fleet health, SLA, and ticket insights.
Access HubSpot Sales Hub data with cross-object queries and property history.
Manage Datto RMM operations and analyze fleet data with local SQLite.
Manage SaaS backups, status checks, and bulk operations through Afi CLI.
Access Huntress APIs and a local SQLite mirror for fleet-wide security insights.
Triage backups, detect stale snapshots, and analyze backup health across engines.
Automate Rootly tasks through Rube MCP to streamline incident response workflows.
Triage RocketCyber alerts, track MTTR, and analyze security posture.
Turn raw log query results into structured incident reports linked to commits and tickets.
Let your AI agent manage PagerDuty alerts, incidents, and on-call workflows.
Safely triage incidents with evidence retrieval, ticket workflows, and notifications.
Search workplace incident data, analyze trends, and draft corrective actions.