Skip to content
PagerDuty logo

PagerDuty MCP server

Incident management workflows for PagerDuty REST API v2.

PagerDuty is not a separate install. One Activepieces MCP server exposes it alongside 770+ other apps, behind a single URL.

Tools
6
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
September 2026

About the PagerDuty MCP server

Connect PagerDuty once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches PagerDuty and 770+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

PagerDuty tools your AI can run

Once connected, your assistant can call any of these PagerDuty actions by asking in plain language.

  • Create Incident

    Create a new PagerDuty incident using the REST API.

    10 fields

  • List Incidents

    List PagerDuty incidents with optional filters and pagination.

    6 fields

  • Get Incident

    Retrieve a PagerDuty incident by ID.

    1 field

  • Acknowledge Incident

    Acknowledge an existing PagerDuty incident.

    2 fields

  • Resolve Incident

    Resolve an existing PagerDuty incident.

    3 fields

  • Custom API Call

    Make a custom API call to PagerDuty REST API v2. Authorization, Accept, and Content-Type headers are injected automatically. For write endpoints that require a From header, add it manually in the headers field.

    10 fields

Triggers

PagerDuty events your agent can watch

These start a run the moment something happens in PagerDuty, so work gets picked up on its own.

  • New Incident

    Triggers when a new incident is created

    1 field

  • Incident Resolved

    Triggers when an incident is resolved.

    1 field

  • Incident Acknowledged

    Triggers when an incident is acknowledged.

    1 field

Give your assistant PagerDuty

Connect PagerDuty once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 770+ other apps. Free to start.

PagerDuty MCP, answered.

No. That is the point of it. One Activepieces server exposes PagerDuty alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect PagerDuty in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 6 tools, including Create Incident, List Incidents, Get Incident, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.