Rootly MCP connector
The Rootly connector brings incidents, on-call schedules and alerts into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about an outage, find similar past incidents, and open or update an incident, each as themselves.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Rootly to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Rootly once
-
Open Connections, choose Add connection, and pick Rootly.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Rootly. Rootly's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Rootly MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Rootly MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Rootly MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Rootly to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Rootly through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Catch up on an incident before joining
Ask what has happened on the incident so far, who is working it and what the latest alerts say, then join the call already up to speed.
-
SRE
Find out who is on call right now
Check the Rootly on-call schedule for a service, see who is covering tonight and who takes over at handoff, without opening the schedule page.
-
Engineering
Find past incidents that look like this one
Describe the symptoms and get the Rootly incidents that looked the same, with what was done last time, so the fix starts from somewhere.
-
Support
Check whether a customer issue is known
Before replying to a ticket, ask whether there is an open Rootly incident touching that service and what the current status says.
-
Security
Open an incident from a suspicious alert
When an alert in Rootly looks like a security event, create the incident, set its severity and add what you know, all from the conversation.
-
Leadership
Prepare the weekly incident review
Pull the incidents from the past week, grouped by severity and service, and get a plain summary ready for the review meeting.
Try asking
- “Who is on call for the payments service right now?”
- “Summarize the open incidents from the last 24 hours.”
- “Find past incidents similar to the checkout latency alert.”
Compare
Elaichi vs Zapier MCP vs Composio for Rootly
All three can connect Rootly to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Rootly tools | Allow or restrict single Rootly tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Rootly call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Rootly gets you
5 screens from the product, each doing one job for your Rootly account.
The agent
Ask about an incident in plain words.
Get answers from live Rootly incidents, on-call schedules and alerts, no dashboard digging.
- incidents
- alerts
- on-call schedules
- incident updates
Ask Elaichi to work across your apps.
Who is on call for the payments service right now?
Summarize the open incidents from the last 24 hours.
Find past incidents similar to the checkout latency alert.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Rootly to every client.
Claude, ChatGPT and Cursor reach Rootly through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Every team gets its own Rootly toolbox.
Scope what Engineering, Support and Security can reach in Rootly, one toolbox each.
- Engineering
- SRE
- Support
- Security
ElaichiToolboxesShared connections
Share one Rootly connection, never a credential.
See who connected each Rootly account and which teams and members work through it.
- Platform
- Payments
- Support
- Security
ElaichiConnectionsAudit log
Every Rootly call is logged with a name.
When, who, what happened and which incident, in an append-only log you can search.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Incident digests run on a schedule.
Rootly incidents are fetched, grouped and drafted into a digest a person approves before posting.
Rootly digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch incidents
Rootly
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Rootly
Queued
Collections and dashboards
Incident health, computed without a model.
Four metrics, fourteen days of Rootly incidents created and a breakdown by team, refreshed on schedule.
Rootly health
Refreshed 4 minutes ago · every 15 minutes · from the incidents collection
Incidents
1,284 ↓ 12%
Alerts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Incidents created
Last 14 days
By team
Share of activity
Platform 34%
Payments 27%
Support 21%
Security 18%
FAQ
Frequently asked questions
How do I connect Rootly to Claude?
In Elaichi, choose Rootly and sign in with your Rootly account; it connects over OAuth, so there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. From that point Claude can reach Rootly incidents, on-call schedules and alerts as you.
Does Rootly work with ChatGPT and Cursor as well as Claude?
Yes. Once Rootly is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Rootly once and every client uses it.
What can an AI agent actually do with my Rootly data?
An agent can look up open and past Rootly incidents, check who is on call for a service, read recent alerts and find earlier incidents that resemble the one in front of you. It can also create a new Rootly incident or update an existing one with what you tell it. Short, concrete asks, such as who is on call for payments, tend to work better than long paragraphs.
Does connecting Rootly give the AI access to every incident and schedule?
No. Every call runs as the person who signed in to Rootly, so the AI sees only the incidents, schedules and alerts that person can already see in Rootly. Elaichi can narrow that access further for a team, and it can never widen it beyond what Rootly itself allows.
Can I stop an agent from deleting or changing things in Rootly?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Rootly incidents and schedules while blocking the actions that create or change them. A restricted action is never advertised to the AI client at all, so no prompt, however worded, can reach it.
What happens to a Rootly connection when someone leaves?
Offboarding that person in Elaichi ends their access to Rootly through every client at once. A shared Rootly connection keeps working for everyone else on the team. If you ever want Rootly gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Rootly MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Rootly is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Rootly?
Yes. Both let Claude, ChatGPT or Cursor use Rootly. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Rootly call.
How is Elaichi different from Composio for Rootly?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Rootly: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Rootly in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.