PagerDuty
PagerDuty hosts its MCP server at https://mcp.pagerduty.com/mcp (US) or https://mcp.eu.pagerduty.com/mcp (EU). The self-hosted server is deprecated. PagerDuty does not support dynamic client registration. The Official card defaults to an API token. OAuth is available if an admin registers an app and pastes its client ID and secret. It is the PagerDuty card with the Official badge. Willow also has a built-in PagerDuty connector.
Some tools need a user token rather than an account token, including incident filters by team or assignee.
API token
- Create a user API key (needs Advanced Permissions) or an account API key.
- In Willow, add the Official PagerDuty card, pick US or EU, and keep API key.
- Paste the key as
Token token=<key>, including theToken token=prefix. PagerDuty rejects a bare bearer token. - Assign groups and Publish.
Everyone who uses this server shares that key's access.
OAuth
Use this when each person should sign in as themselves.
- In PagerDuty, go to Integrations → App Registration → New App.
- Add Scoped OAuth. Set the redirect URL to the URI from Willow's setup step.
- Include at least
users.read. Add the other scopes the tools need. - Copy the Client ID and Client Secret.
- In Willow, switch the Official card to OAuth sign-in and paste both.
- Each person clicks Check connection and approves the app.
Troubleshooting
Every call returns 401
Cause: The API key was pasted without the Token token= prefix, or the header is Bearer.
Solution: Set the key to Token token= followed by the token, with that exact spacing.