Rootly + clariBI
Connect Rootly through clariBI's MCP catalog. Read-only OAuth, and incident timelines sitting next to the support load and revenue impact each outage causes.
Native Rootly connector via the MCP catalog.
Connect with OAuth, keep the access read-only, and ask questions across Rootly and your other tools in plain English. The setup is the same one-click flow as Google Analytics, Stripe, Meta Ads, or Jira.
What is Rootly?
Rootly is an incident-management platform. Teams declare incidents, set severity, coordinate the response, page on-call responders, and write retrospectives when it is over.
clariBI reaches your Rootly workspace through its hosted MCP server: incidents and their severity, response and resolution timelines, on-call schedules, and retrospective records. Reads inherit the connected user's access, and clariBI never changes an incident.
Learn more at rootly.com
Connect Rootly in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source → MCP Servers tab. Find Rootly in the catalog and click Connect.
Authorize with Rootly (OAuth)
A Rootly sign-in opens in your browser. Approve the read access. clariBI uses Dynamic Client Registration, so there is no Rootly app to set up, and credentials are Fernet-encrypted at rest.
Ask questions, get dashboards
clariBI surfaces incident counts, severity mix, and time-to-resolve. Ask "How many Sev1s this quarter and what was our MTTR?" and the AI engine queries Rootly alongside your support and revenue data.
What you can analyze
Out of the box with the Rootly MCP connector:
- Incident count and severity mix over time
- Mean time to acknowledge and mean time to resolve
- Incidents per service or team
- Outage duration for a specific incident
- Responder load and on-call coverage
- Cross-source: incident windows → support ticket spikes → revenue dips
Rootly is one of 90+ vendors in the clariBI MCP catalog. See the full list →
What the AI engine can call
clariBI discovers Rootly's tool surface at connection time and exposes the read-only tools to the planner. Write or configuration tools are filtered out by the catalog's read-only heuristic, so the connector stays analytical.
When you connect, clariBI lists the tools your Rootly MCP server advertises and keeps the read-only ones: reading incidents, severities, timelines, schedules, and retrospectives.
Anything that would change Rootly is excluded at the catalog layer and never reachable through clariBI.
See the live tool list once connected, or read the setup guide →
Cross-source questions Rootly makes possible
Rootly data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Rootly × Support
"Do our Sev1 incidents line up with spikes in support tickets?"
Planner: read Sev1 incident windows from Rootly, then count support tickets in those windows from your support tool and chart the overlap.
Rootly × Stripe
"What did the longest outage last quarter cost us?"
Planner: find the longest incident in Rootly, then sum failed or missing Stripe charges over its duration.
Rootly connector FAQ
Do I need to register an app with Rootly?
No. clariBI uses Dynamic Client Registration (RFC 7591), so Rootly issues the connection credentials at connect time. You do not manage any keys in clariBI.
Can clariBI declare or change incidents?
No. The catalog exposes read tools only, and the read-only heuristic filters out anything that writes. clariBI reads incidents, timelines, and schedules; it never declares, edits, or resolves them.
Which clariBI plan includes the Rootly connector?
MCP integrations are available on the Trial, Starter, Professional, and Enterprise plans. You can connect Rootly during the free 14-day trial.
Start your free trial and connect Rootly in a minute
OAuth in, read-only, dashboards in seconds.
Start free trial