PagerDuty

Live

OAUTH 2.0

INCIDENT MANAGEMENT

Monitoring

Every on-call schedule, alert, and incident your engineering team manages lives in PagerDuty. PagerDuty MCP gives your agent authenticated access to incident data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the PagerDuty account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: Permissions enforced. 90-day audit trail.
PagerDuty
agent · Acme Q3
Run
What critical incidents are open right now and which services are affected?
S
pagerduty_incidents_list
61ms
Incident management agent
2 critical incidents open. payment-service (P1 #4201, 23 min, assigned K. Moore). auth-gateway (P1 #4198, 51 min, assigned J. Lee). Both acknowledged, pending resolution.
Sources: 2 P1 incidents, live
pagerdutymcp
2 incidents
18:29
Message Claude...

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

CALL ANY TOOL
List and create incidents, retrieve timelines, resolve alerts, check services, and see on-call schedules.
pagerduty_team_get
Team get
Get details of a specific PagerDuty team by its ID.
Parameters
Name
Type
Required
Description
id
string
Required
The ID of the team to retrieve.
pagerduty_tags_list
Tags list
pagerduty_user_get
User get
pagerduty_tag_create
Tag create
pagerduty_teams_list
Teams list
pagerduty_vendor_get
Vendor get
pagerduty_users_list
Users list
pagerduty_service_get
Service get
pagerduty_team_create
Team create
pagerduty_team_delete
Team delete
pagerduty_team_update
Team update
pagerduty_user_create
User create
pagerduty_user_delete
User delete
pagerduty_user_update
User update
pagerduty_incident_get
Incident get
pagerduty_oncalls_list
Oncalls list
pagerduty_schedule_get
Schedule get
pagerduty_vendors_list
Vendors list
pagerduty_incident_merge
Incident merge
pagerduty_services_list
Services list
pagerduty_service_create
Service create
pagerduty_abilities_list
Abilities list
pagerduty_service_delete
Service delete
pagerduty_incidents_list
Incidents list
pagerduty_service_update
Service update
pagerduty_schedules_list
Schedules list
pagerduty_incident_create
Incident create
pagerduty_incident_manage
Incident manage
pagerduty_incident_update
Incident update
pagerduty_incident_snooze
Incident snooze
Build your Agent
Drop the toolkit in, point it at the user, and your incident management agent can use PagerDuty from the first run.
Python · LlamaIndex
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 });
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 }],
});
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 Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
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
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
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.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""pagerduty"": {
""url"": ""https://mcp.scalekit.com/pagerduty"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.pagerduty]
url = ""https://mcp.scalekit.com/pagerduty""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""pagerduty"": {
""url"": ""https://mcp.scalekit.com/pagerduty"",
""type"": ""http""
}
}
}