PagerDuty · Cursor
Add the PagerDuty MCP server to Cursor
Look up incidents, services, schedules and on-call, and act on incidents.
Official serverLocalObservability & incidents
1. Add the server
Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"pagerduty": {
"command": "uvx",
"args": [
"pagerduty-mcp",
"--enable-write-tools"
]
}
}
}2. Sign in
Cursor prompts you to sign in the first time a remote OAuth server is used. PagerDuty runs locally; set any credentials PagerDuty asks for before starting Cursor.
3. Try it
Ask Cursor for something PagerDuty can do. Look up incidents, services, schedules and on-call, and act on incidents. Approve the first tool call and check the result before allowing write actions automatically.
- · Remote servers take a url; local servers take command and args.
- · Values can reference ${env:NAME} so secrets stay out of the file.
FAQ
- How do I add the PagerDuty MCP server to Cursor?
- Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.
- Is this the official PagerDuty MCP server?
- Yes. It is published by PagerDuty as io.github.PagerDuty/pagerduty-mcp in the official MCP registry.
- Does the PagerDuty MCP server need an API key?
- It runs locally from a package. See PagerDuty's docs for any credentials it needs.
Links
PagerDuty in other clients
More observability & incidents for Cursor
Work at PagerDuty?
Feature PagerDuty across the directory and its category from $49/month.
Reviewed Oct 5, 2026. Command generated from the registry record and checked against Cursor's documented syntax.