# 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.

Source: https://elaichi.ai/connectors/rootly/

## Facts

| | |
| --- | --- |
| Application | Rootly |
| Category | Incident Management |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Rootly builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@rootly.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Rootly is connected

- 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.

## Connect Rootly in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Rootly.
2. Optionally set Share with, then press Connect.
3. Approve it in Rootly. Rootly's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Rootly tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Rootly MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Rootly to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Rootly tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Rootly through Elaichi

### Catch up on an incident before joining

Engineering. 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.

### Find out who is on call right now

SRE. 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.

### Find past incidents that look like this one

Engineering. Describe the symptoms and get the Rootly incidents that looked the same, with what was done last time, so the fix starts from somewhere.

### Check whether a customer issue is known

Support. Before replying to a ticket, ask whether there is an open Rootly incident touching that service and what the current status says.

### Open an incident from a suspicious alert

Security. 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.

### Prepare the weekly incident review

Leadership. Pull the incidents from the past week, grouped by severity and service, and get a plain summary ready for the review meeting.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Rootly connection?

Yes. One person connects Rootly in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so every incident they read or update is logged under their own name.

### 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.