ChatGPT + PagerDuty: What the Integration Can (and Can't) Do in 2026
Yes — there’s no PagerDuty app in the ChatGPT apps directory, but PagerDuty runs an official, PagerDuty-hosted remote MCP server at mcp.pagerduty.com/mcp (EU: mcp.eu.pagerduty.com/mcp) that ChatGPT can use as a custom connector. Nothing to deploy: point ChatGPT at the endpoint, authenticate with a PagerDuty User API token, and you can query incidents, dig through services, and check on-call schedules in plain English. There’s also an open-source local server if you’d rather run it yourself. The irony to keep in view: PagerDuty is the most trigger-driven product in your stack, and ChatGPT only works in a session you’re driving — it will never wake up because a page fired.
Here’s what the ChatGPT PagerDuty integration actually does, how to turn it on, and what to use when you want incident work that runs without you.
What ChatGPT can actually do with PagerDuty
- Interrogate incidents conversationally. “What P1s hit the checkout service this month, and what was the common thread?” — answered from your real incident data, with follow-up questions working like any chat.
- Check on-call state. “Who’s on call for the payments escalation policy this weekend?” beats clicking through schedules.
- Manage services and schedules. The server exposes write tools too — PagerDuty’s docs cover retrieving incident data, managing services, and updating on-call schedules — so ChatGPT can make changes you ask for, with your token’s permissions.
- Draft the postmortem. Pull an incident’s timeline and notes, then have ChatGPT turn them into a first-draft retro doc in the same session.
- Run inside agent sessions. With ChatGPT Work (launched July 9, 2026), you can @-mention connectors and have an agent cross-reference a quarter of incidents against your services for a reliability review — one long, metered run that you start.
How to set it up
- In PagerDuty, generate a User API token (your account needs Advanced Permissions; the token inherits your access, so scope accordingly).
- In ChatGPT, on a plan with connector support, open Settings → Apps & Connectors and add a custom connector pointing at
https://mcp.pagerduty.com/mcp— orhttps://mcp.eu.pagerduty.com/mcpif your account lives in the EU service region. - Provide the User API token when prompted — the hosted server authenticates via an Authorization header, streamable HTTP, nothing to install.
- Ask something (“show me open incidents on the API service”) or @-mention the connector in a prompt.
The limits that actually matter
- It will never respond to a page. This is the gap that defines the whole pairing. Incidents are events; ChatGPT has no triggers. Nobody is opening a chat window at 3am to ask ChatGPT what’s on fire — the value of incident tooling is what happens automatically in the first five minutes, and a chat connector contributes nothing to that window.
- Your token, your blast radius. The User API token carries your full permissions, including writes. An agent-mode run that “helpfully” reschedules an on-call override is a real failure mode — consider a least-privilege user for the token.
- Session-bound, even in agent mode. ChatGPT Work runs are long and autonomous but manually started and metered against your plan’s allowance — good for a reliability review, useless as a standing incident responder.
- Follow-through stops at the chat. ChatGPT can summarize an incident beautifully; it won’t post that summary to your status channel, notify the account team, or open the follow-up tickets.
If you want PagerDuty work that runs on its own: Carly
Everything valuable in incident response happens on a trigger: the incident fires, and context needs to move — to Slack, to the on-call engineer, to the customer-facing team — before anyone has finished reading the page.
That’s where Carly fits. Carly is an AI executive assistant that acts on triggers across your whole stack, set up by conversation instead of code:
- Fires on events and schedules, 24/7, in the cloud. Incident triggered, incident resolved, Monday 9am — Carly acts without a chat open.
- First-five-minutes context, automatically. When a PagerDuty incident fires on the checkout service, Carly posts a summary to #incidents in Slack with recent Sentry errors and the current on-call engineer tagged, and emails a heads-up to the customer success lead if the affected service is customer-facing.
- The paperwork nobody does. When an incident resolves, Carly creates a Linear ticket for the postmortem, drafts the timeline from the incident log, and schedules the retro on the team’s calendar.
- Weekly reliability digest. Every Monday, Carly emails engineering leadership last week’s incident count, MTTR, and repeat offenders — no dashboard safari required.
- Connects to anything — 200+ native integrations, plus any other tool via your own API key.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations — and Carly natively integrates with PagerDuty.
ChatGPT vs Carly
| ChatGPT (PagerDuty MCP connector) | Carly | |
|---|---|---|
| Query incidents, services, on-call | Yes | Yes |
| Draft a postmortem on request | Yes | Yes |
| Posts context to Slack when an incident fires | No | Yes, on the trigger |
| Notifies the right people at 3am | No | Yes |
| Weekly incident digest, unprompted | No | Yes, on a schedule |
| Runs without a session open | No (agent runs are started + metered) | Yes (cloud, 24/7) |
| Opens follow-up tickets, schedules the retro | No | Yes |
| Setup | Add connector + User API token | Describe it in plain English |
| Pricing | Paid ChatGPT plan | AI agents from $35/mo |
ChatGPT with PagerDuty’s MCP server is an incident analyst you question after the fact. Carly is the responder that moves context the moment the page fires.
Frequently Asked Questions
Does ChatGPT work with PagerDuty?
Yes. PagerDuty operates an official hosted remote MCP server at mcp.pagerduty.com/mcp (EU accounts: mcp.eu.pagerduty.com/mcp). Add it to ChatGPT as a custom connector and authenticate with a PagerDuty User API token — no self-hosting required, though an open-source local server also exists on GitHub.
Can ChatGPT respond to a PagerDuty incident automatically?
No. ChatGPT has no triggers — it queries PagerDuty only inside sessions you start, so it can’t react when an incident fires. For “when a P1 hits, post context to Slack and notify the right people,” you need a trigger-based assistant like Carly.
Can ChatGPT modify my PagerDuty schedules and services?
Yes, within your token’s permissions — PagerDuty’s MCP server covers managing services and updating on-call schedules, not just reads. That cuts both ways: the User API token inherits your access, so consider a least-privilege user before letting agent-mode runs loose on it.
How do I connect ChatGPT to PagerDuty?
Generate a User API token in PagerDuty (Advanced Permissions required), then add https://mcp.pagerduty.com/mcp as a custom connector in ChatGPT’s settings and supply the token. Ask about incidents or @-mention the connector in a prompt.
More: ChatGPT MCP · What is ChatGPT Work · ChatGPT Work limits · ChatGPT + Slack · Claude + PagerDuty
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
