Set up the PagerDuty MCP server

PagerDuty's MCP server lets AI agents manage incidents, query on-call schedules, update services, and trigger workflows directly in your PagerDuty account. This guide covers connecting PagerDuty's hosted MCP server to Mintive with OAuth, where each user signs in to PagerDuty, or with a User API Token each user pastes in.

Prerequisites

• A Mintive admin account
• A PagerDuty account with Advanced Permissions enabled
• For OAuth, a PagerDuty user with the Manager, Global Admin, or Account Owner base role to register the OAuth app

Add PagerDuty to Mintive

OAuth (recommended)

Each user signs in to PagerDuty and approves the connection, so PagerDuty applies that person's own permissions, and nobody has to create or rotate a personal token. PagerDuty's MCP server doesn't support dynamic client registration, so Mintive connects through an OAuth app you register in PagerDuty.

Register the OAuth app in PagerDuty

1. In PagerDuty, go to Integrations > Developer Tools > App Registration and click New App.

2. Enter a Name such as Mintive and a Description, select OAuth 2.0 under Functionality, and click Next.

3. Under Authorization, choose the OAuth type:

   Type	What users can grant	Use when
   Scoped OAuth	Read or write access you pick per resource (incidents, services, schedules, and so on)	You want to limit what agents can do, for example read-only access
   Classic User OAuth	Read, or read and write, across all PagerDuty resources	You want agents to act with the user's full PagerDuty permissions

4. Click Add Redirect URL and enter the callback for your Mintive region. Add it now, because PagerDuty doesn't let you edit the redirect URL of a Scoped OAuth app after it's registered.

   Mintive region	Redirect URL
   US	https://app.mintmcp.com/oauth/callback
   EU	https://eu.mintmcp.com/oauth/callback

5. Under Permission Scope, select the access agents need. For Scoped OAuth, select Read Access only on the resources agents should read and add Write Access only where they need to make changes.

6. Click Register App, then copy the Client ID and Client Secret. PagerDuty shows the secret only once, so store it before you click Continue.

Install the connector in Mintive

1. In Mintive, go to MCP store and open the Catalog tab.

2. Select PagerDuty to open its configuration panel and choose OAuth as the authentication method.

3. Under OAuth Client Advanced Settings, paste the Client ID and Client Secret from your PagerDuty app.

4. Keep Override OAuth endpoints checked with its prefilled values:

   Field	Value
   Authorization URL	https://app.pagerduty.com/global/oauth/authorize
   Token URL	https://app.pagerduty.com/global/oauth/token
   Scopes	Leave empty, so the permissions you set on the PagerDuty app apply
   Token Endpoint Auth Method	client_secret_post

   PagerDuty only accepts the client secret in the request body for Scoped OAuth apps, so the sign-in fails if Token Endpoint Auth Method is set to anything other than client_secret_post.

5. Click Install.

When a user first connects, PagerDuty shows a consent screen listing the permissions your app allows. After they click Submit Consent, Mintive stores and refreshes their token.

API token

Use a User API Token when you can't register an OAuth app. The token carries the full permissions of the user who generated it, and each user who connects must generate their own.

Generate a PagerDuty User API Token

1. In PagerDuty, click your User Profile icon in the top-right corner and select My Profile.
2. Click the User Settings tab.
3. In the API Access section, click Create API User Token.
4. Enter a description (for example, Mintive) and click Create Key.
5. Copy the token immediately, because PagerDuty shows it only once, then click Close.

Install the connector in Mintive

1. In Mintive, go to MCP store and open the Catalog tab.
2. Select PagerDuty to open its configuration panel and choose API token as the authentication method.
3. Click Install.

Each user pastes their own User API Token when they first connect, and Mintive sends it as Authorization: Token token=<token> on every request.

EU service region

The connector points at https://mcp.pagerduty.com/mcp, which serves US accounts. If your PagerDuty account is in the EU service region, open the installed connector's Settings > Connection and change MCP Server URL to https://mcp.eu.pagerduty.com/mcp. The OAuth endpoints stay the same for both regions.

Security considerations

• Authentication: With OAuth, every request runs as the signed-in user through the authorization code flow with PKCE, and Mintive stores and refreshes the tokens, so users never handle a PagerDuty credential. With API tokens, each user's token is stored encrypted and sent on every request.
• Authorization: PagerDuty enforces the user's own role on every call. A Scoped OAuth app narrows that further to the resources and access levels you selected, which makes it the way to give agents read-only access.
• Credential lifetime: PagerDuty User API Tokens don't expire automatically, so rotate them periodically under My Profile > User Settings > API Access. OAuth grants last until the user disconnects in Mintive or you revoke them in PagerDuty.
• Revocation: Account owners and admins can revoke any user's API token from the PagerDuty admin console, and Revoke All Tokens on the OAuth app's Client tab ends every OAuth grant at once.
• Data exposure: PagerDuty's hosted MCP server processes live incident and schedule data, so restrict Mintive access to users who need it and use tool customization to hide tools agents shouldn't call.

Troubleshooting

• Sign-in fails with invalid_grant: invalid code verifier: the token request is sending the client secret in a way PagerDuty rejects. Open the connector's OAuth Client Advanced Settings, check Override OAuth endpoints, set the Authorization URL and Token URL listed above, set Token Endpoint Auth Method to client_secret_post, save, and have the user reconnect.
• Sign-in fails with a redirect_uri error: the redirect URL on the PagerDuty app doesn't match the callback for your Mintive region exactly. If it's a Scoped OAuth app whose redirect URL can't be edited, register a new app with the right URL and update the client ID and secret in Mintive.
• The consent screen lists more access than agents need: the PagerDuty app allows it. Edit the app's Permission Scope in PagerDuty, then have users reconnect so a new token is issued.
• Requests fail with 401 when using an API token: the token was revoked or mistyped. Generate a new one and reconnect.

Next steps

• Tool customization: Control which PagerDuty tools reach your users
• MCP gateway administration: Manage access and permissions