PagerDuty MCP | OAuth 2.0 PagerDuty connector for AI agents

CALL ANY TOOL

List and create incidents, retrieve timelines, resolve alerts, check services, and see on-call schedules.

pagerduty_incidents_list

List incidents

List PagerDuty incidents filtered by status, urgency, and team.

Parameters

Name

Type

Required

Description

status

string

Optional

Filter: triggered, acknowledged, resolved

urgency

string

Optional

Filter: high, low

limit

integer

Optional

Max incidents to return

pagerduty_incident_get

Get incident

pagerduty_incident_create

Create incident

pagerduty_incident_resolve

Resolve incident

pagerduty_services_list

List services

pagerduty_oncalls_list

List on-call schedules

Build your Agent

Drop the toolkit in, point it at the user, and your incident management agent can use PagerDuty from the first run.

Copied

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pagerduty"], toolNames: ["pagerduty_incidents_list", "pagerduty_incident_get", "pagerduty_incident_create"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

Copied

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pagerduty"], toolNames: ["pagerduty_incidents_list", "pagerduty_incident_get", "pagerduty_incident_create"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["pagerduty"], toolNames: ["pagerduty_incidents_list", "pagerduty_incident_get", "pagerduty_incident_create"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

Copied

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/pagerduty",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start using PagerDuty.

Incidents & alerts

Copy the prompt

Copied

List all open P1 incidents right now.

Copy the prompt

Copied

Get full timeline for incident [id].

Copy the prompt

Copied

Which incidents have been open for over 1 hour?

Copy the prompt

Copied

Resolve incident [id] with note: [text].

Services & on-call

Copy the prompt

Copied

Which services have open incidents?

Copy the prompt

Copied

Who is on call for [service] right now?

Copy the prompt

Copied

List all escalation policies for [team].

Copy the prompt

Copied

Get all services with high-urgency alerts.

Reporting

Copy the prompt

Copied

How many P1 incidents occurred this week?

Copy the prompt

Copied

Average resolution time for [service] last month.

Copy the prompt

Copied

List incidents resolved in under 30 minutes.

Copy the prompt

Copied

Which service has the most incidents this quarter?

SEE HOW AUTH WORKS

Users authorize PagerDuty once. Their credentials stay vaulted, every call is checked, and every action is logged.

1

Authorize

Your user connects

PagerDuty

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

2

Store

Their

PagerDuty

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

3

Resolve

When your agent calls a

PagerDuty

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

4

Audit

Every

PagerDuty

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Same per-user auth pattern across other incident management agents and MCP connectors. Working code, live demos, fork what fits.

ENGINEERING

DevOps assistant agent

Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.

ENGINEERING

Engineering standup agent

Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

PagerDuty today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access PagerDuty as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the PagerDuty oauth 2.0 stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in PagerDuty?

Yes. Pass a tool name filter to listScopedTools so the incident management agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches PagerDuty.

What happens when a user revokes PagerDuty access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent page a team or trigger escalations?

Only if the authorizing user has PagerDuty permissions to escalate. Responders can acknowledge and resolve; managers can create and escalate. PagerDuty role-based permissions apply to every agent call.

PagerDuty

Tools your incident management agent reaches for on PagerDuty, scoped per user.