The PagerDuty connector lets your workflows talk to PagerDuty’s hosted MCP server — a remote MCP endpoint maintained by PagerDuty that exposes their incidents, services, schedules, escalation policies, and on-call surface.Documentation Index
Fetch the complete documentation index at: https://docs.spojit.com/llms.txt
Use this file to discover all available pages before exploring further.
Spojit does not curate the tool list — PagerDuty does. For the live set of tools and their parameters, see the PagerDuty MCP integration guide.
Connection setup
Generate a User API Token
Sign in to PagerDuty, click your avatar (top-right), choose My Profile, then open the User Settings tab. Click Create API User Token, give it a label, and copy the token.PagerDuty distinguishes between User API tokens (act as you, see only what you can see) and General Access tokens (account-wide). The MCP server requires a User API token — General Access tokens will not authenticate.
Caveats
- EU-region accounts. This connector is configured for PagerDuty’s US-region MCP endpoint (
mcp.pagerduty.com/mcp). PagerDuty hosts a separate EU endpoint (mcp.eu.pagerduty.com/mcp) for EU-region accounts — get in touch if you need EU-region routing. - The token acts as you. Every MCP call is attributed to the user who created the token. Use a dedicated service account (rather than a personal account) if you want incidents and audit logs to be clearly machine-driven.
- Token has no expiry. User API tokens stay valid until you revoke them in My Profile → User Settings. Rotate them if you suspect compromise.
- MCP endpoint is hosted by PagerDuty. Availability, rate limits, and the exact tool surface are determined by PagerDuty. Outages and breaking changes are upstream.