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

Source: https://elaichi.ai/connectors/pagerduty/

## Facts

| | |
| --- | --- |
| Application | PagerDuty |
| Category | Incident Management |
| AI tools | 157 |
| Authentication | OAuth or API key |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once PagerDuty is connected

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

## Connect PagerDuty in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick PagerDuty.
2. Optionally set Share with, 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.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which PagerDuty tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## PagerDuty MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## PagerDuty MCP connector for Microsoft Copilot

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

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

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a PagerDuty tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with PagerDuty through Elaichi

### Open an incident from a customer report

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

### Find out who is on call right now

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

### Catch the incident up after the bridge

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

### Review every open incident across services

IT operations. 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.

### Adjust the rota without editing by hand

Engineering managers. 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.

### Check who holds a PagerDuty license

IT operations. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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, 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 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 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.

## All 157 PagerDuty tools

Every tool below is callable through https://api.elaichi.ai/mcp once PagerDuty is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **List all PagerDuty licenses** (List). List licenses associated with your account in PagerDuty. Returns license details including id, type, and status.
- **List all PagerDuty license allocations** (List). List license allocations in PagerDuty. Returns licenses allocated to users within your account including user and license details.
- **List all PagerDuty user licenses** (List). Get the license allocated to a user in PagerDuty. Requires the user id. Returns license details including license type and status.
- **List all PagerDuty schedules** (List). List on-call schedules in PagerDuty. Returns schedules array with schedule details including name and time periods users are on-call.
- **Get single PagerDuty schedule by ID** (Get). Get detailed information about a schedule in PagerDuty by id. Returns id, name, description, time_zone, schedule_layers with entries, escalation_policies, users, teams, and URLs for the schedule.
- **Create a PagerDuty schedule** (Create). Create a new on-call schedule in PagerDuty with name, type, time_zone, description, and schedule_layers. Returns id, type, summary, self URL, html_url, escalation_policies, users, teams, schedule_layers, overrides_subschedule, and final_schedule.
- **Update a PagerDuty schedule by ID** (Update). Update an existing on-call schedule in PagerDuty by id. Returns the updated schedule including id, name, time_zone, description, schedule_layers, escalation_policies, users, teams, overrides_subschedule, and final_schedule.
- **Delete a PagerDuty schedule by ID** (Delete). Delete a schedule by id in PagerDuty. Returns no content on success.
- **List all PagerDuty users on call** (List). List all users on call in a given schedule using id. Returns users array with user details for the specified schedule.
- **List all PagerDuty on calls** (List). List all on-call entries in PagerDuty filtered by escalation_policy_ids, schedule_ids, user_ids, since, and until. Returns on-call periods with user, escalation policy, and schedule details.
- **Create a PagerDuty incident** (Create). Create an incident in PagerDuty with required fields: type, title, service, priority, and escalation_policy. Returns incident id, title, status, incident_number, urgency, service, priority, escalation_policy, assignments, and URLs.
- **List all PagerDuty incidents** (List). List existing incidents in PagerDuty. Returns incidents representing problems or issues that need resolution. Key response fields include incident id, status, urgency, and assigned users.
- **Get single PagerDuty incident by ID** (Get). Get detailed information about a specific incident in PagerDuty by id. Returns fields including id, summary, incident_number, title, status, created_at, updated_at, service, assignments, escalation_policy, teams, urgency, and more.
- **Update a PagerDuty incident by ID** (Update). Update an incident by id in PagerDuty. Returns updated incident fields including id, summary, status, title, incident_number, created_at, updated_at, service, priority, assignments, acknowledgements, resolved_at, urgency, and escalation_policy.
- **List all PagerDuty me** (List). Get details about the current user in PagerDuty. Returns user information including id, name, email, and role.
- **List all PagerDuty services** (List). List existing services in PagerDuty. Returns service id, name, description, status, escalation policies, and teams associated with each service.
- **Get single PagerDuty service by ID** (Get). Get details about a specific service in PagerDuty by id. Returns fields including id, type, summary, name, status, escalation_policy, teams, integrations, incident_urgency_rule, support_hours, scheduled_actions, and auto_pause_notifications_parameters.
- **Create a PagerDuty service** (Create). Create a new service in PagerDuty with required escalation_policy. Returns id, name, status, escalation_policy, incident_urgency_rule, support_hours, scheduled_actions, and auto_pause_notifications_parameters.
- **Update a PagerDuty service by ID** (Update). Update an existing service by id in PagerDuty. Returns updated service fields including id, name, status, escalation_policy, incident_urgency_rule, support_hours, scheduled_actions, integrations, teams, and auto_pause_notifications_parameters.
- **Delete a PagerDuty service by ID** (Delete). Delete a service by id in PagerDuty. Once deleted, the service is inaccessible and new incidents cannot be created for it.
- **List all PagerDuty incident types** (List). List available incident types in PagerDuty filtered by enabled state. Returns incident_types array with details like type name and status.
- **Get single PagerDuty incident type by ID** (Get). Get detailed information about a single incident type in PagerDuty using id. Returns enabled, id, parent, name, type, description, created_at, updated_at, and display_name fields.
- **Create a PagerDuty incident type** (Create). Create a new incident type in PagerDuty with required fields name, display_name, and parent_type. Returns fields enabled, id, name, parent, type, description, created_at, updated_at, and display_name.
- **Update a PagerDuty incident type by ID** (Update). Update an Incident Type by id in PagerDuty. Returns fields: id, name, created_at, updated_at, description, display_name, enabled, parent, and type.
- **List all PagerDuty abilities** (List). List all abilities available to your PagerDuty account. Returns an array of ability names such as 'teams' and 'urgencies'.
- **List all PagerDuty add ons** (List). List all installed Add-ons in PagerDuty. Returns id, type, summary, self URL, html_url, name, and src for each Add-on.
- **Get single PagerDuty add on by ID** (Get). Get details about an existing Add-on in PagerDuty by id. Returns fields id, type, name, src, and services with service details including id, type, summary, self, and html_url.
- **Create a PagerDuty add on** (Create). Install an Add-on with name and src in PagerDuty. Returns id, type, summary, self URL, html_url, name, and src of the installed Add-on. HTTPS required for src.
- **Update a PagerDuty add on by ID** (Update). Update an Add-on by id in PagerDuty. Requires id, and addon object with type, name, and src. Returns updated add-on with id, type, name, src, and services array.
- **Delete a PagerDuty add on by ID** (Delete). Delete an Add-on by id in PagerDuty. Removes an existing Add-on which adds new functionality to PagerDuty's UI. Returns 204 on successful deletion.
- **List all PagerDuty alert grouping settings** (List). List all alert grouping settings in PagerDuty. Returns id, name, description, type, config, services, created_at, and updated_at fields for each setting.
- **Get single PagerDuty alert grouping setting by ID** (Get). Get an Alert Grouping Setting by id in PagerDuty. Returns id, name, description, type, config, services, created_at, and updated_at fields. Note: features available only on certain plans.
- **Create a PagerDuty alert grouping setting** (Create). Create a new Alert Grouping Setting in PagerDuty. Returns id, name, description, type, config, services, created_at, and updated_at fields of the created setting.
- **Update a PagerDuty alert grouping setting by ID** (Update). Update an Alert Grouping Setting by id in PagerDuty. Returns the updated setting including id, name, description, type, config, services, created_at, and updated_at fields.
- **Delete a PagerDuty alert grouping setting by ID** (Delete). Delete an existing Alert Grouping Setting by id in PagerDuty. Returns 204 on successful deletion.
- **List all PagerDuty audit records** (List). List audit records matching query parameters in PagerDuty. Returns records sorted by execution_time with fields id, execution_time, method, root_resource, action, and details. Supports cursor and limit for pagination.
- **List all PagerDuty automation actions** (List). List Automation Actions in PagerDuty filtered by optional parameters. Returns id, name, description, action_type, creation_time, modify_time, privileges, and services fields for each action.
- **Get single PagerDuty automation action by ID** (Get). Get an Automation Action by id in PagerDuty. Returns fields including id, name, description, action_type, creation_time, modify_time, invocation permissions, and associated services and teams.
- **Create a PagerDuty automation action** (Create). Create an Automation Action in PagerDuty with name, description, action_type, and action_data_reference.script. Returns action id, name, description, action_type, action_data_reference.script, creation_time, modify_time, invocation permissions, services, and teams.
- **Update a PagerDuty automation action by ID** (Update). Update an Automation Action by id in PagerDuty. Returns updated action with fields id, name, description, action_type, action_data_reference.script, creation_time, modify_time, and invocation permissions.
- **Delete a PagerDuty automation action by ID** (Delete). Delete an Automation Action by id in PagerDuty. Returns no content on successful deletion.
- **List all PagerDuty invocations** (List). List invocations filtered by action_id, incident_id, invocation_state, or not_invocation_state in PagerDuty. Returns id, type, action_id, action_snapshot, duration, metadata, runner_id, state, and timing for each invocation.
- **Get single PagerDuty invocation by ID** (Get). Get an Automation Action Invocation by id in PagerDuty. Returns id, type, action_id, action_snapshot with name and action_type, duration, metadata with agent and incident ids, runner_id, state, and timing of state transitions.
- **Create a PagerDuty invocation** (Create). Create an invocation for an action in PagerDuty using id and metadata with incident_id. Returns invocation id, type, action_snapshot with name and type, runner_id, timing states, duration, state, action_id, and metadata including agent and incident details.
- **List all PagerDuty automation action runners** (List). List Automation Action runners in PagerDuty. Returns runners with fields id, name, description, creation_time, type, runner_type, runbook_base_uri, status, teams, and privileges. Results sorted by runner name.
- ...and 107 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
