Skip to main content
All PagerDuty integration capabilities

​
About

This is an MCP connector that gives the Sazabi agent tools from PagerDuty’s hosted MCP server. You connect it with a PagerDuty REST API key, which Sazabi stores securely and sends as the Authorization: Token token=<key> header. The agent sees only what that key can see, and Sazabi connects it read-only: tools that change PagerDuty data stay blocked. This connector reads PagerDuty. The PagerDuty capability that routes Sazabi issues to a service as alerts is set up separately. What the agent can do:
  • Read incidents with their alerts, notes, log entries, and change events
  • Look up who is on call, schedules, and escalation policies for a service
  • Review services, teams, and business service dependencies
  • Pull incident metrics such as time to acknowledge and time to resolve

​
Prerequisites

  • A PagerDuty account with permission to create a REST API key
  • Your PagerDuty region — United States (*.pagerduty.com) or Europe (*.eu.pagerduty.com); you select it when connecting. A key only works in its own region.

​
Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.
1

​
Create a REST API key

In PagerDuty, open Integrations > API Access Keys, click Create New API Key, tick Read-only API Key, and copy the key. PagerDuty shows it once.
2

​
Open the connector

Find PagerDuty in Settings > MCP connectors.
3

​
Connect

Select your region, paste the key, and connect. Sazabi stores the key securely and sends it as the Authorization header.

​
Set up with the CLI

You can also connect PagerDuty with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference). PagerDuty authenticates with a REST API key sent as an Authorization header:
For Europe accounts, add --server-url https://mcp.eu.pagerduty.com/mcp. Sazabi uses this connector read-only, so write tools stay blocked even without --read-only; pass --project-id <project> to target a specific project. Confirm the result with sazabi mcp-connectors list.

​
Verify

Open the connector’s connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm you selected the region your PagerDuty account runs in.

​
Troubleshooting

Connection fails with an authorization error — PagerDuty rejected the key. Check that you copied the whole key and that it was created in the same region you selected (a US key does not work against the EU server). No tools discovered — Disconnect and reconnect from Settings > MCP connectors with a fresh key. A tool returns a permission error — The key cannot see that data. Create a key with access to it.

​
Further reading

Agent tools

How the agent uses connector tools.

MCP connectors

Browse the connector catalog.