Skip to content

PagerDuty MCP connector

The PagerDuty connector lets Claude, ChatGPT, Cursor, and any MCP client work with your PagerDuty incidents, services, schedules, and on-call rotations, with each person signed in as themselves and every action recorded.

  • How it connects. OAuth or API key. 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 PagerDuty to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect PagerDuty once

  1. Open Connections, choose Add connection, and pick PagerDuty.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Supply your own PagerDuty app, then approve. PagerDuty needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

pagerduty
PagerDuty
Better Stack
Chronosphere
FireHydrant
Freshservice
Freshstatus
2

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.

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

PagerDuty 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 today. The plugin directory lives at chatgpt.com/plugins.

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

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

Use cases

What teams do with PagerDuty through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Open an incident from a customer report

    When a customer reports an outage, describe it in plain words and have an incident created on the right PagerDuty service, with the title and urgency set, without leaving the chat.

  • Engineering

    Find out who is on call right now

    Ask who is on call for a given service or schedule and get the name straight from PagerDuty, including who picks up next, instead of hunting through rotations.

  • Engineering

    Catch the incident up after the bridge

    Once the call ends, have the incident acknowledged or resolved and its details updated in PagerDuty so the record matches what actually happened.

  • IT operations

    Review every open incident across services

    Pull the list of open and acknowledged incidents across all PagerDuty services, grouped by service or urgency, and get a plain-language summary before the morning standup.

  • Engineering managers

    Adjust the rota without editing by hand

    Create a new schedule or update an existing PagerDuty schedule when someone is on leave, and confirm the change by asking who is now covering that week.

  • IT operations

    Check who holds a PagerDuty license

    List PagerDuty licenses and see which people they are allocated to, then review or update user details so seats match the team you actually have.

Try asking

  • “Who is on call this weekend across payments schedules?”
  • “Summarize incidents opened for the checkout service this week.”
  • “List users with no PagerDuty license allocation.”

See all 157 PagerDuty tools below

Compare

Elaichi vs Zapier MCP vs Composio for PagerDuty

All three can connect PagerDuty 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 PagerDuty, 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 PagerDuty tools Allow or restrict single PagerDuty 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 PagerDuty 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.

AI tools

PagerDuty tools for your AI agents

157 tools are ready to call through Elaichi's MCP endpoint the moment you connect PagerDuty, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting PagerDuty gets you

6 screens from the product, each doing one job for your PagerDuty account.

The agent

Ask about on-call in plain language.

Type a question and get answers from live PagerDuty schedules, incidents and users.

  • incidents
  • schedules
  • users
  • licenses

Ask Elaichi to work across your apps.

Who is on call this weekend across payments schedules?

Summarize incidents opened for the checkout service this week.

List users with no PagerDuty license allocation.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One PagerDuty endpoint, every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

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

Tool catalog

157 PagerDuty tools ready on connect.

Schedules, users, sessions, licenses and on-call resources, with no custom code to write.

  • List all PagerDuty users
  • Get single PagerDuty user by ID
  • Delete a PagerDuty user by ID
  • Update a PagerDuty user by ID
ElaichiTools
Tool Action Description
List all PagerDuty users List List users in PagerDuty account. Returns users' id, name, email, and role fields. Supports filtering by query parameter 'query'.
Get single PagerDuty user by ID Get Get details about a specific user in PagerDuty by id. Returns user fields including id, name, email, role, time_zone, job_title, avatar_url, description, teams, contact_methods, and notification_rules.
Delete a PagerDuty user by ID Delete Delete a user by id in PagerDuty. Returns 400 if the user has assigned incidents unless offboarding feature is enabled and configured. Incident reassignment is asynchronous and not guaranteed before response.
Update a PagerDuty user by ID Update Update a user by id in PagerDuty. Requires user object with name and email. Returns updated user fields including type, name, email, time_zone, color, role, job_title, avatar_url, and description.
List all PagerDuty user sessions List List active sessions of a PagerDuty user by id. Returns sessions array with details of each active session. Note: active sessions exclude newly issued OAuth tokens since November 2021.

Toolboxes

Each team gets its own toolbox.

Curate PagerDuty toolboxes per team so on-call reaches the people who own it.

  • Platform engineering
  • Site reliability
  • Support
  • IT operations
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

PagerDuty · schedules and escalation policies

PagerDuty starter 18 Mar 4, 2026

Site reliability toolbox

PagerDuty · incidents and on-call rotations

— 9 Mar 2, 2026

Support toolbox

PagerDuty · incidents and services

— 24 Feb 27, 2026

IT operations toolbox

PagerDuty · users and licenses

PagerDuty starter 6 Feb 19, 2026

Security toolbox

PagerDuty · user sessions and audit records

— 31 Jan 30, 2026

Engineering management toolbox

PagerDuty · teams and on-call coverage

— 12 Jan 22, 2026

Shared connections

Teammates use PagerDuty without a credential.

See who connected each account and how many teams and members share it.

  • Platform EMEA
  • Site reliability
  • Support tier one
  • IT operations
ElaichiConnections
Connection Scope Status Access
PA

PagerDuty (Platform EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PA

PagerDuty (Site reliability)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PA

PagerDuty (Support tier one)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PA

PagerDuty (IT operations)

Connected by Tyler Reed

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

PagerDuty (Security response)

Connected by Ryan Hayes

Personal • Active Not shared
PA

PagerDuty (Payments on-call)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every PagerDuty call is on record.

When, who, what happened, type and resource, appended and never edited.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

PagerDuty Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

PagerDuty Incidents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

PagerDuty Incidents List Toolbox

Launching 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

A schedule fires, the digest ships.

Fetch PagerDuty incidents, group them, draft a digest, approve, then post it back.

PagerDuty 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

    PagerDuty

    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 Michael Brennan

    Approve
  6. Post the digest

    PagerDuty

    Queued

Collections and dashboards

PagerDuty health, counted not guessed.

Four metrics, 14 days of incidents created and a team breakdown, refreshed on schedule.

PagerDuty health

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

Live

Incidents

1,284 ↓ 12%

Schedules

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Incidents created

Last 14 days

By team

Share of activity

Platform EMEA 34%

Site reliability 27%

Support tier one 21%

IT operations 18%

FAQ

Frequently asked questions

How do I connect PagerDuty to Claude?

First connect PagerDuty in Elaichi. PagerDuty needs an OAuth application registered inside your own PagerDuty account, so one administrator creates it there and enters its client ID and secret in Elaichi a single time; after that, each person simply signs in to PagerDuty with their own account when prompted. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in, and your PagerDuty incidents, schedules, and services are available in the conversation.

Does PagerDuty work with ChatGPT and Cursor as well as Claude?

Yes. Once PagerDuty is connected in Elaichi, the same address, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect PagerDuty once and every client you use sees it.

What can an AI agent actually do with my PagerDuty data?

With PagerDuty connected, an agent can look up open incidents and their details, open a new incident on a service, acknowledge or resolve one, and update its title or urgency. It can tell you who is on call for a service or schedule, create or change schedules, and review services, users, and license allocations. Because PagerDuty exposes many actions, short concrete asks work best, such as who is on call for payments right now.

Does connecting PagerDuty give the AI access to every service and team?

No. Every call to PagerDuty runs as the person who signed in, so the agent can only see the services, incidents, and schedules that person already has access to in PagerDuty. Elaichi can narrow that further with restrictions, but it can never grant more than the person's own PagerDuty account allows.

Can my team share one PagerDuty connection?

Yes. One administrator connects PagerDuty in Elaichi and shares the connection with a team, so nobody else has to touch the OAuth application or any API key. Each teammate still signs in to PagerDuty as themselves, so incidents they open or resolve are attributed to them and the audit log names the actual person.

Can I stop an agent from deleting or changing things in PagerDuty?

Yes. In Elaichi you restrict PagerDuty actions individually, so you can allow reading incidents and on-call schedules while blocking deleting users or schedules, or block every change and keep it read-only. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, accidental or otherwise, can trigger it.

What happens to a PagerDuty connection when someone leaves?

Offboarding that person in Elaichi ends their access to PagerDuty through every client immediately. A PagerDuty connection shared with a team keeps working for everyone else, even if the person who first set it up is the one leaving. If you want PagerDuty gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Does the PagerDuty MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. PagerDuty 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 PagerDuty?

Yes. Both let Claude, ChatGPT or Cursor use PagerDuty. 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 PagerDuty call.

How is Elaichi different from Composio for PagerDuty?

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 PagerDuty: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put PagerDuty in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor 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.