PagerDuty MCP connector
The PagerDuty connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- OAuth or API key
- Free 14-day trial
- No credit card
Who is on call this weekend across payments schedules?
Working in PagerDuty with Elaichi
-
List all PagerDuty users
-
Get single PagerDuty user by ID
-
List all PagerDuty user sessions
How to connect PagerDuty to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
PagerDuty 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.
PagerDuty MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
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.
PagerDuty 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. The plugin directory lives at chatgpt.com/plugins.
PagerDuty 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.
PagerDuty MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
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 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.
What teams do with PagerDuty through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in PagerDuty is logged.
-
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.”
What connecting PagerDuty gets you
6 screens from Elaichi, each doing one job for your PagerDuty account.
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, Cursor or Microsoft Copilot
The agent
Ask about on-call in plain language.
Type a question and get answers from live PagerDuty schedules, incidents and users.
Copy the endpoint
AI apps
One PagerDuty endpoint, every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.
Tool catalog
157 PagerDuty tools ready on connect.
Schedules, users, sessions, licenses and on-call resources, with no custom code to write.
Toolboxes
Each team gets its own toolbox.
Curate PagerDuty toolboxes per team so on-call reaches the people who own it.
Shared connections
Teammates use PagerDuty without a credential.
See who connected each account and how many teams and members share it.
Audit log
Every PagerDuty call is on record.
When, who, what happened, type and resource, appended and never edited.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
PagerDuty digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
PagerDuty
Queued
Automations
A schedule fires, the digest ships.
Fetch PagerDuty incidents, group them, draft a digest, approve, then post it back.
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%
Collections and dashboards
PagerDuty health, counted not guessed.
Four metrics, 14 days of incidents created and a team breakdown, refreshed on schedule.
For IT and engineering
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.
| 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 | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting deleting users or schedules, or restrict every change and keep it read-only. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, 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 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 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