Skip to content

Rootly MCP connector

The Rootly connector brings incidents, on-call schedules and alerts into Claude, ChatGPT, Cursor, Microsoft Copilot 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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Who is on call for the payments service right now?

Working in Rootly with Elaichi

  • Looked in Rootly
Ask anything…
Governance / Audit log Last 24 hours
Rootly Looked in Rootly Emily Carter · Claude · 9:41 AM Done
Rootly Looked in Rootly Megan Brooks · ChatGPT · 9:38 AM Done
Rootly Looked in Rootly Ryan Hayes · Cursor · 9:35 AM Done

How to connect Rootly to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Rootly MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Rootly MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Rootly MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Rootly MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Rootly to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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.

What teams do with Rootly through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Rootly is logged.

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

What connecting Rootly gets you

5 screens from Elaichi, each doing one job for your Rootly account.

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about an incident in plain words.

Get answers from live Rootly incidents, on-call schedules and alerts, no dashboard digging.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint brings Rootly to every client.

Claude, ChatGPT, Cursor and Microsoft Copilot reach Rootly through one governed endpoint, no SDK, no shared key.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Rootly · incidents and alerts

Rootly starter 18 Mar 4, 2026

SRE toolbox

Rootly · on-call schedules and alerts

— 9 Mar 2, 2026

Support toolbox

Rootly · customer-facing incident status

— 24 Feb 27, 2026

Security toolbox

Rootly · security incidents and alerts

Rootly starter 6 Feb 19, 2026

Customer success toolbox

Rootly · incident status for key accounts

— 31 Jan 30, 2026

Leadership toolbox

Rootly · incident trends and reviews

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Rootly toolbox.

Scope what Engineering, Support and Security can reach in Rootly, one toolbox each.

ElaichiConnections
Connection Scope Status Access
RO

Rootly (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
RO

Rootly (Payments)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
RO

Rootly (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
RO

Rootly (Security)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
RO

Rootly (SRE EMEA)

Connected by Ryan Hayes

Personal • Active Not shared
RO

Rootly (Executive)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Rootly connection, never a credential.

See who connected each Rootly account and which teams and members work through it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Rootly Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Rootly Incidents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Rootly Incidents List Toolbox

Audit log

Every Rootly call is logged with a name.

When, who, what happened and which incident, in an append-only log you can search.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Rootly digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch incidents

    Rootly

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Rootly

    Queued

Workflows

Incident digests run on a schedule.

Rootly incidents are fetched, grouped and drafted into a digest a person approves before posting.

Rootly health

Refreshed 4 minutes ago · every 15 minutes · from the incidents collection

Live

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%

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.

Why connect Rootly's MCP server through Elaichi

Rootly builds and runs this MCP server. Elaichi sits in front of it, so Rootly's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Rootly's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Rootly's tools at the same Elaichi address as every other connected app. Nobody adds Rootly's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Rootly sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Rootly's server. By default, a tool Rootly does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Rootly

    Rootly builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Rootly team.

    [email protected]

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Rootly, by what to check
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 Free for one person; $15 per user per month on Gold. 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.

Questions, answered

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, Microsoft Copilot, 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 role, 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 restricting the actions that create or change them. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot