PagerDuty MCP server
PagerDuty collects operational signals, alerts the right on-call responder, and coordinates incident response across engineering teams. Ops and SRE teams use it to reduce time to resolution. Connect through Arc0 to use the actions your identity is allowed to call.
Agent workflows for PagerDuty.
List incidents
Use when triaging incidents for a service. Defaults to the last month, so older open incidents may be absent. Supply since/until together for an explicit window of at most six calendar months. Filter by service and status.
Get incident
Use when inspecting a known incident before deciding whether to acknowledge or resolve it. Returns incident state and service reference without responder personal details.
List incident notes
Use when reading the operational notes on a known incident or checking whether an earlier note was saved before retrying an uncertain write.
8 PagerDuty actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
5Look things up, subject to your permissions.
- pagerduty.list_incidentsList incidents
Use when triaging incidents for a service. Defaults to the last month, so older open incidents may be absent. Supply since/until together for an explicit window of at most six calendar months. Filter by service and status.
- pagerduty.get_incidentGet incident
Use when inspecting a known incident before deciding whether to acknowledge or resolve it. Returns incident state and service reference without responder personal details.
- pagerduty.list_incident_notesList incident notes
Use when reading the operational notes on a known incident or checking whether an earlier note was saved before retrying an uncertain write.
- pagerduty.list_servicesList services
Use when finding service identifiers and operational status before filtering incidents. Returns one bounded page without integration credentials or responder contact details.
- pagerduty.list_oncallsList on-calls
Use when checking coverage for one known user in a bounded time window. Returns structural user and schedule references without names, email addresses or contact methods.
write
3Create and change things. Allow, or ask the user first.
- pagerduty.add_incident_noteAdd incident note
Use when adding an internal operational note visible to incident responders. Integrations may notify watchers; do not use for customer messages. If the outcome is unknown, read notes before retrying to avoid duplicates.
- pagerduty.acknowledge_incidentAcknowledge incident
Use when taking responsibility for a triggered incident; responders may be notified. Reads first and refuses resolved incidents: PagerDuty would reopen and assign them to you. Already acknowledged is a no-op. State can race after the read; read back before retrying.
- pagerduty.resolve_incidentResolve incident
Use when the incident is confirmed fixed. Resolves it and may notify responders and subscribers; do not use merely to silence an unresolved problem. Read incident state before retrying an unknown outcome.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Control access to PagerDuty.
Connect the intended PagerDuty account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- pagerduty.add_incident_note: require approval
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How PagerDuty connects.
Connect PagerDuty using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use PagerDuty with your AI client.
Sign in to Arc0 and connect PagerDuty in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
PagerDuty with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingPagerDuty with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingPagerDuty with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingPagerDuty with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingPagerDuty with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingPagerDuty with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
PagerDuty and Arc0, answered.
Does PagerDuty work with Claude Desktop and Claude Code?
Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.
Can I use PagerDuty with OpenAI Codex, ChatGPT and Cursor?
Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.
Is this the official PagerDuty MCP server?
This is Arc0’s integration page, not a claim of an official PagerDuty server. Arc0 adds a shared connection, policy and audit experience across apps. Consult PagerDuty for its own current MCP offerings.
Which PagerDuty actions are supported?
8 registry-defined actions: 5 read, 3 write and 0 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.
Which permissions does PagerDuty need?
Connect PagerDuty using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
Can I restrict writes in PagerDuty?
You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.
What does PagerDuty through Arc0 cost?
See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.
Plug PagerDuty into your agent.
PagerDuty MCP server: 8 actions including list incidents, get incident, list incident notes. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
PagerDuty and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by PagerDuty.