How to use PagerDuty with Cursor
You want PagerDuty inside Cursor so it can triage active incidents, find the right on-call responder, investigate an incident timeline, and reassign and resolve incidents safely — without you copy-pasting between tabs. Here is the whole setup, once.
Create your PagerDuty gateway
The gateway is the thing Cursor connects to, and it is where you decide which PagerDuty tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your PagerDuty tools
In the dashboard, create a gateway and pick the PagerDuty tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your PagerDuty tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these PagerDuty prompts
Cursor can now act on your PagerDuty account. Click a prompt to copy it.
Set permissions so an agent can inspect incidents and on-call schedules without acknowledging, resolving, or reassigning them. Pair it with Contextual Access policies to require approval before incident changes reach PagerDuty.