Incident Management
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.
In Elaichi
Connect PagerDuty once
-
Open Connections, choose Add connection, and pick PagerDuty.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect PagerDuty to 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.
Connect PagerDuty to 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.
Connect PagerDuty to 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 PagerDuty 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 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.”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
Audit log
Every PagerDuty call is on record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch incidents
PagerDuty
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
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
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 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.
Put PagerDuty in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.