Skip to main content
Activation required. AI access management must be enabled for your tenant before you can use it. To get started, contact the C1 support team for a walkthrough.
C1 can govern PagerDuty access two ways. Both let your AI clients read from and act on PagerDuty through governed MCP tools, but they come from different places and appear as two separate entries in your MCP server catalog:
  • PagerDuty MCP — listed as plain PagerDuty in your catalog. C1 registers PagerDuty’s own hosted MCP server (mcp.pagerduty.com) as a downstream server C1 governs. Authenticate with per-user OAuth — using a Scoped OAuth application you register manually in PagerDuty, since PagerDuty’s hosted MCP server doesn’t support dynamic client registration (DCR) — or with a shared API key or user token. Tool calls run with whichever identity you authenticated.
  • PagerDuty API — C1 hosts its own MCP server that translates PagerDuty’s REST API into tools. You choose between per-user OAuth or a shared REST API key, and access is scoped to the OAuth app’s granted scopes or the REST API key’s permissions.
Use the native PagerDuty MCP option (listed as plain PagerDuty in your catalog) if you want PagerDuty’s own broader, agentic tool set and you’re prepared to manually register a Scoped OAuth application (or use an API key). Use PagerDuty API if you’d rather scope access purely through PagerDuty’s REST API scopes with either credential type.
C1 registers as a client of PagerDuty’s own hosted MCP server (PagerDuty MCP Server) rather than translating PagerDuty’s REST API itself. Your users’ AI clients still only ever see C1-governed MCP tools, but C1 proxies each tool call straight through to mcp.pagerduty.com/mcp under the connected identity, then returns the result. The tools available are exactly the ones PagerDuty’s own MCP server exposes — C1 doesn’t reshape or add to them.

​
Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • For per-user OAuth, you need permission to register a Scoped OAuth application in PagerDuty — this requires an account admin or owner role. Regular users are limited to Classic User OAuth, which C1 doesn’t use here, since it only supports coarse and unreliable access.
  • For an API key or user token, you need a PagerDuty account that can create a REST API key, or your own user account to create a personal token.
  • PagerDuty’s hosted MCP server doesn’t support OAuth dynamic client registration (DCR). Unlike some other native MCP integrations, per-user OAuth here always starts with an application you register yourself — there’s no automatic client registration to skip.
In your MCP server catalog, this option is listed as PagerDuty — distinct from the PagerDuty API entry, which connects through C1’s own MCP server. If you don’t see either, contact the C1 support team to enable it for your tenant.

​
Option 1: Set up per-user OAuth

With per-user OAuth, you register one Scoped OAuth application in PagerDuty and each user authorizes individually. This keeps every action attributable to the user who took it, within the scopes you granted.

​
Register a Scoped OAuth application

Register the application in PagerDuty before configuring authentication in C1.
1
In PagerDuty, go to Integrations > App Registration and select New App. Give it a name that identifies C1 for your team, such as C1. See PagerDuty’s Register an App documentation.
2
Select OAuth 2.0 as the app’s functionality, then leave Scoped OAuth selected on the next screen — it’s the default and the only mode with the granular, per-object scopes below. The other option, Classic User OAuth, only supports coarse read (and unreliable write) access, so C1 doesn’t use it.
3
Set the Redirect URL exactly to:
4
Select the scopes C1 needs. For full functionality, grant:
  • incidents.read, incidents.write — view, create, acknowledge, resolve, and update incidents
  • services.read, services.write — view, create, and update services
  • teams.read, teams.write — view, create, and update teams and their memberships
  • users.read, users.write — view, create, and update users
  • schedules.read, schedules.write — view, create, and update on-call schedules
  • oncalls.read — view who is currently on call
  • escalation_policies.read — view escalation policies
  • event_orchestrations.read, event_orchestrations.write — view, create, and update event orchestrations (the rules that route events to services)
  • status_pages.read, status_pages.write — view, create, and update status pages
  • webhook_subscriptions.read, webhook_subscriptions.write — view, create, and update webhook subscriptions
  • change_events.read — view change events (deployments and other changes correlated with incidents)
  • incident_workflows.read, incident_workflows:instances.write — view incident workflow definitions, and run workflow instances
  • extension_schemas.read — view extension schemas used by service extensions and integrations
  • openid — sign in with OpenID Connect; identifies the authorizing user
You can narrow or widen this list later from the same screen.
5
Select Register App, then copy the Client ID and Client Secret from the confirmation dialog. PagerDuty shows the secret only once.

​
Register the server with OAuth

With your Scoped OAuth application ready, register the server and provide your credentials:
1
Follow Register an MCP server and select PagerDuty from the catalog.
2
When you configure authentication, choose OAuth2 — per-user passthrough and enter your application’s client ID and client secret.
3
Save your changes. The first time a user calls a PagerDuty tool from their AI client, they’re redirected to PagerDuty to sign in (if they aren’t already) and approve the connection, then returned to C1.

​
Option 2: Use an API key or user token

An API key or user token authenticates every user as one shared PagerDuty identity. Use this when per-user attribution in PagerDuty isn’t required, or when you’d rather skip registering an OAuth application.
1
In PagerDuty, go to Integrations > API Access Keys and select Create New API Key — or, for a personal token, go to your user icon, then My Profile > User Settings > API Access > Create API User Token. See PagerDuty’s API Access Keys documentation.
2
Give the key a recognizable description such as C1, then copy it. PagerDuty shows it only once.
3
Follow Register an MCP server and select PagerDuty from the catalog.
4
When you configure authentication, choose Bearer token and paste your API key or user token.
5
Save your changes. C1 starts a sync that discovers the tools the PagerDuty MCP server exposes.
PagerDuty doesn’t use the standard Bearer prefix for this credential — it expects the Authorization header formatted as Token token=<key> (source). C1 sends it in this format automatically; you don’t need to enter the prefix yourself.

​
What access is granted

Tool calls run with whichever identity you authenticated: for per-user OAuth, the connected user’s own PagerDuty permissions within the scopes you granted; for an API key or user token, the permissions attached to that credential. Either way, access spans PagerDuty’s own tool set — incidents, services, on-call schedules, escalation policies, teams, event orchestrations, status pages, and more.

​
How PagerDuty MCP credentials are shared

How PagerDuty sees your users’ activity depends on the method you chose:
  • Per-user OAuth. Each user authorizes with their own PagerDuty account, so tool calls run under that user’s PagerDuty identity and inherit only the scopes you granted. PagerDuty attributes each action to the individual user.
  • API key or user token. Every user’s tool calls use the one credential you provided, so PagerDuty sees a single shared identity. C1 still attributes each call to the individual user in the AI tool usage audit log.

​
Discover and govern tools

After you register the server, C1 runs tool discovery against PagerDuty’s hosted MCP server. Discovered tools appear on the server’s Tools tab.Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCP > Settings. See Require tool approval and Default tool classification.Before anyone can call a PagerDuty tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if authentication isn’t complete yet, so seeing discovered tools doesn’t confirm a user has authorized or that credentials are valid. You confirm access when an approved user successfully calls a PagerDuty tool from their AI client.

​
Manage access to PagerDuty MCP

  • Rotate the OAuth client secret in your PagerDuty app under Integrations > App Registration, then update the secret on the server’s authentication settings in C1.
  • Rotate an API key or user token by creating a new one in PagerDuty and updating it in C1, then delete the old one.
  • Revoke access from the app’s page in App Registration — revoke its tokens to invalidate every session at once, or delete the app entirely.
  • Adjust scopes by editing them on the OAuth application in PagerDuty, or by choosing a read-only versus full-access API key.