PagerDuty MCP for AI Agents. Manage critical alerts and service health instantly.
PagerDuty MCP lets your AI agent take full control of incident response and service health tracking. You can list, create, acknowledge, or resolve incidents across all services without leaving your IDE. It also provides real-time visibility into on-call schedules, allowing you to instantly identify who is responsible for an alert, making critical outage management conversational.
Give Claude and any AI agent real-world access
List current, acknowledged, or resolved incidents across your entire service portfolio.
Acknowledge, resolve, or update the severity of an existing incident programmatically.
View detailed configurations for specific services or retrieve profiles and contact information for team members.
See who is currently assigned to handle alerts across all defined schedules and escalation levels in real time.
Generate a new incident record when an event occurs, requiring only the service ID and title.
Ask an AI about this
Waiting for input…
What AI agents can do with PagerDuty with 11 Tools
This MCP provides a comprehensive set of tools allowing you to list, create, update, and retrieve all critical PagerDuty resources, from users to services.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using PagerDuty MCPCreate Incident
Starts a new incident record for a specified service using your email and a title.
Get Incident
Retrieves detailed status information about a specific, existing incident ID.
Get Service
Fetches the full configuration and integration details for one monitored service.
Get User
Gets detailed profile information for a single team member within PagerDuty.
List Oncalls
Provides a real-time list of all individuals currently scheduled to be on call...
List Schedules
Retrieves a comprehensive list of all defined on-call rotation schedules.
List Services
Lists every service that is currently monitored by PagerDuty.
List Users
Retrieves a complete list of all user accounts within the connected PagerDuty...
Update Incident
Changes an incident's status, such as acknowledging it, resolving it, or reassigning...
List Escalation Policies
Shows all existing escalation policies and their defined routing rules for incidents.
List Incidents
Lists multiple incidents, allowing you to filter by status like 'triggered' or...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with PagerDuty, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by PagerDuty. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Pain of the Incident War Room Solved with Vinkius AI Gateway
When an outage hits, you're forced into a rapid cycle of context switching. You jump from the monitoring dashboard to the user directory, then open the service configuration page, and finally switch to the incident tracker just to acknowledge it. Copying IDs, cross-referencing schedules, and manually updating status across tabs is exhausting.
With this MCP, that process collapses into a single conversation. Your agent gathers all the necessary data—service configurations via get_service, current on-call details from list_oncalls, and active incident reports using list_incidents—and hands you an immediate action plan. You don't click; you talk.
Achieve Instant Incident Management with PagerDuty
The manual steps that vanish include checking the list of active incidents, figuring out which team owns the service using get_user, and then having to manually change the status from 'triggered' to 'acknowledged'.
Now you can tell your agent to acknowledge an incident and retrieve the full service context in one prompt. The entire lifecycle moves at your pace, not the pace of clicking through ten different tabs.
What your AI can actually do with this
You manage complex incident lifecycles using natural conversation through this MCP. Instead of jumping between multiple dashboards, your agent handles the full workflow. You can list all active incidents and get deep details on a specific service's configuration or user profile. Need to know who is currently covering the platform? The MCP checks current on-call rotations, showing which level (L1, L2) has coverage until what date.
If something goes wrong, your agent creates the initial incident record automatically, then you can acknowledge it and update its status when troubleshooting is done. It's a command center for service health—all accessible from any MCP-compatible client through Vinkius.
019d75ee-2ade-73c6-b403-b225ff91edf1 Here's how it actually works
The bottom line is you get a single conversational interface that handles the full lifecycle of an alert, from discovery to resolution.
First, connect your PagerDuty account credentials by entering your REST API Key into Vinkius.
Next, ask your AI agent to check the status of critical services or list users to gather necessary context for an outage.
Finally, tell the agent what needs to happen—for example, 'Acknowledge incident XYZ and find out who is on-call'—and it runs the workflow.
Who is this actually for?
This MCP is for the Site Reliability Engineer who needs instant incident data without leaving their terminal. It's also perfect for DevOps teams automating runbooks or Engineering Managers needing quick visibility into on-call coverage during a crisis.
Uses the MCP to triage live alerts, quickly getting service details and updating incident statuses directly from their coding environment.
Automates complex incident workflows, such as listing services and creating new incidents when a monitoring hook triggers an alert.
Checks who is on-call for specific teams or reviews escalation policies to understand the immediate response structure during an outage.
What Changes When You Connect
You get instant visibility into who is on-call. Instead of checking a wiki or calling someone, asking the agent to list_oncalls tells you exactly which team member is responsible right now.
Incident resolution accelerates when you can acknowledge it and gather details simultaneously. Use update_incident after getting service data from get_service; no context switching required.
Debugging outages gets easier because your AI client pulls all the necessary information—from listing services to checking escalation policies—in one conversation thread.
You never have to manually create an incident again. If a monitoring hook triggers, simply ask the agent to create_incident with the service ID and title, logging it immediately.
It cuts down on manual lookup time. Need to know who owns Service X? Use get_user or list_users combined with list_services to find contact info instantly.
See it in action
Handling a sudden production alert
The agent detects an outage and runs 'list_incidents'. You tell it to check the associated service using get_service, confirming its critical status. Next, you ask who is on-call using list_oncalls to assign immediate ownership via update_incident.
Post-outage reporting
A manager needs a report on last week's downtime. The agent runs list_incidents, filtering by resolved status, and then pulls all related service details using get_service for the executive summary.
Onboarding a new team member
A new engineer asks about coverage gaps. The agent lists_schedules to show the entire rotation pattern and runs list_escalation_policies so they understand how incidents flow through teams.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating PagerDuty as a general dashboard
Trying to manually find out which team is responsible for an alert by clicking deep into the web UI's user management section.
Instead, let your agent list_oncalls first. It gives you the current on-call person immediately, bypassing all manual navigation and dashboard clicks.
Ignoring incident status updates
Having to manually log into PagerDuty and change an alert from 'triggered' to 'acknowledged', wasting time in a confusing UI.
Just use update_incident. It changes the status programmatically, logging the action right where you are working.
Confusing services with users
Trying to find a team member's contact info by looking through service configurations.
Keep user lookups separate. Use list_users or get_user to confirm roles and contact methods before troubleshooting any service issue.
When It Fits, When It Doesn't
Use this MCP if your core pain point is incident response speed, especially when multiple pieces of information—like who's on-call, what the service configuration is, and what incidents are active—are needed simultaneously. It excels at running multi-step workflows (e.g., list_services -> get_service -> update_incident). Don't use it if you only need to read a static report or perform basic ticket logging outside of an alert context; for that, a standard ticketing system integration is better. However, if your process involves reacting to real-time alerts and needing instant team coordination data, this MCP is essential.
Questions you might have
How do I use PagerDuty MCP to see who is on-call? +
Simply ask your agent to list_oncalls. It immediately provides real-time data showing the current L1 and L2 contacts, along with their expiration dates.
Can I create a new incident using the PagerDuty MCP? +
Yes, use create_incident. You just need to provide your service ID and a title, and it registers the alert immediately.
What if an incident status needs changing? Which tool should I use in PagerDuty MCP? +
Use update_incident. This function lets you acknowledge, resolve, or escalate an incident programmatically with a single command.
How does the PagerDuty MCP help me monitor services? +
You can list all monitored services using list_services, and then drill down into any specific one by calling get_service to view its full configuration details.
Powerful workflows you can unlock today
MCP Recipe for Instant Incident War Rooms
PagerDuty wakes you up at 2am with 'high error rate' but the Axiom dashboard shows 47 different error types , your agent already ran the query, found the root cause, and posted the diagnosis before you opened your laptop
Run Incident Response From Discord via MCP
PagerDuty fires, Datadog provides the evidence, Discord becomes the war room , nobody opens three browser tabs at 3am anymore