MCP Directory

How to add PagerDuty MCP to Cursor

PagerDuty's official MCP server — agents triage incidents, manage on-call schedules, and query services from your IDE. Paste the config into ~/.cursor/mcp.json and restart Cursor.

Last updated June 14, 2026 · 72★ · stdio · apikey · official

Cursor config for PagerDuty MCP

uvx pagerduty-mcp
{
  "mcpServers": {
    "pagerduty-mcp": {
      "command": "uvx",
      "args": [
        "pagerduty-mcp"
      ],
      "env": {
        "PAGERDUTY_USER_API_KEY": "<your-pagerduty-user-api-token>"
      }
    }
  }
}

Requires `uv` (the Python package runner). Install it from https://docs.astral.sh/uv/ if `uvx` is not found.

Setup steps

  1. 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
  2. 2Paste the PagerDuty MCP config below into the "mcpServers" object.
  3. 3Fill in placeholder secrets, then save.
  4. 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
  5. 5Ask Cursor to use one of PagerDuty MCP's tools to confirm it's connected.

Before you start

  • uv installed globally — the standard config launches the server with uvx
  • A PagerDuty User API Token: profile icon → My Profile → User Settings → API Access → Create API User Token
  • EU-hosted accounts: PAGERDUTY_API_HOST=https://api.eu.pagerduty.com in env

What PagerDuty MCP can do in Cursor

list_incidents

Lists incidents with filtering

get_incident

Retrieves a specific incident

manage_incidents

Updates incident status, urgency, assignment, or escalation level (write)

create_incident

Creates a new incident (write)

add_note_to_incident

Adds a note to an incident (write)

add_responders

Adds responders to an incident (write)

list_incident_notes

Lists all notes for a specific incident

list_alerts_from_incident

Lists all alerts for an incident with pagination

Security

The server acts with the full permissions of whichever user's API token you configure; it starts read-only and only exposes write tools when launched with --enable-write-tools, and Claude Desktop stores the token in plaintext config, so restrict file permissions. EU accounts must set PAGERDUTY_API_HOST=https://api.eu.pagerduty.com or requests go to the US API.

PagerDuty MCP + Cursor FAQ

Where is the Cursor config file?

Cursor reads MCP servers from ~/.cursor/mcp.json. Paste the PagerDuty MCP config there under the "mcpServers" key and restart the client.

Is PagerDuty MCP safe to use with Cursor?

The server acts with the full permissions of whichever user's API token you configure; it starts read-only and only exposes write tools when launched with --enable-write-tools, and Claude Desktop stores the token in plaintext config, so restrict file permissions. EU accounts must set PAGERDUTY_API_HOST=https://api.eu.pagerduty.com or requests go to the US API.

Is the PagerDuty MCP server official and free?

Yes — it lives in PagerDuty's GitHub org under an Apache-2.0 license and costs nothing beyond your PagerDuty subscription, since it just calls the normal REST API with your User API Token. Support is community-based (GitHub issues and the PagerDuty forum), not part of paid support.

Can it modify or delete things in my PagerDuty account?

Not unless you opt in. The server starts in read-only mode; write tools like create_incident, manage_incidents, delete_team, and status page posts only register when you launch it with the --enable-write-tools flag.

Does it work with EU-hosted PagerDuty accounts?

Yes — set PAGERDUTY_API_HOST=https://api.eu.pagerduty.com in the env block. Without it the server defaults to https://api.pagerduty.com and EU tokens will fail to authenticate.

View repo Full PagerDuty MCP page