Skip to content
Vinkius

PagerDuty Connector for AI agents.

11 live capabilities

Manage production incidents and on-call rotations from your AI client.

Live agent request PagerDuty / Connector

Waiting for input…

AI Agent

Why people use PagerDuty

PagerDuty for Faster Incident Response

With this Connector, you just type Acknowledge the database alert into your AI client. The agent handles the lookup and the status update for you. You stay in your flow while the work gets done.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a direct line to your incident management platform inside your favorite AI client.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Emergency Triage

    An SRE asks for all triggered incidents and then acknowledges the most critical one to start the fix.

  2. Real-world use case 02

    Shift Handover

    A manager asks who is on-call for the Platform team to see who needs to be looped in during a shift change.

  3. Real-world use case 03

    Service Auditing

    A DevOps lead lists all services to check if a new integration is active and correctly configured.

Complete set · 11capabilities

The complete PagerDuty capability set.

These are the exact actions your AI can choose when you ask it to work with PagerDuty.

Capability set01 / 03

01—04

4 capabilities in this set.

Part of 11 available through PagerDuty.

  1. 01 Capability

    List schedules

    List every on-call rotation schedule in your account. You can use this to see coverage windows and handoff times.

  2. 02 Capability

    List services

    See a list of every monitored service in your account. It's the fastest way to browse your entire service inventory.

  3. 03 Capability

    List users

    Get a list of all users in your PagerDuty account. Use this for auditing your team members or checking permissions.

  4. 04 Capability

    Update incident

    Change an incident's status to acknowledged, resolved, or escalated. This allows you to manage the lifecycle of an alert programmatically.

Capability set02 / 03

05—08

4 capabilities in this set.

Part of 11 available through PagerDuty.

  1. 05 Capability

    Create incident

    Create a new incident on a specific service. You just need to provide the service ID, title, and your user email.

  2. 06 Capability

    Get incident

    Pull up all the details for a specific incident. This is useful for seeing the full history and current status of an alert.

  3. 07 Capability

    Get service

    View the configuration of a specific service. It shows you the integrations, health status, and other settings.

  4. 08 Capability

    Get user

    Pull the profile for a specific user. You can see their contact methods and notification rules in one place.

Capability set03 / 03

09—11

3 capabilities in this set.

Part of 11 available through PagerDuty.

  1. 09 Capability

    List escalation policies

    See all the escalation chains for your teams. It helps you understand how incidents route through different groups.

  2. 10 Capability

    List incidents

    Pull a list of all incidents across your services. You can even filter them by status like triggered or acknowledged.

  3. 11 Capability

    List oncalls

    See who is currently on-call across all your schedules. This helps you quickly identify the right person to contact.

Set up in minutes

One URL. Then ask PagerDuty to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use PagerDuty from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_UeCWwWxqx7aZZue1T0HK7vi7AgO8v9VtsWaLEvhs/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it PagerDuty, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable PagerDuty for the conversation.

Where the request belongs

Work PagerDuty can move forward.

Built around the request

The SRE who's tired of context-switching between their terminal and the PagerDuty dashboard during a 2 AM outage. It's for people who need to act fast on production issues.

01

SRE Engineer

Triages active alerts and updates incident statuses while staying in their IDE.

02

Engineering Manager

Gets a quick pulse on active incidents and on-call coverage without opening a browser.

03

DevOps Specialist

Automates routine incident updates and checks service health.

When one Connector is not enough

Combine PagerDuty with the systems that finish the task.

View all recipes
01

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

 02

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

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
PagerDuty Incident Trigger logo
01 1 capability

PagerDuty Incident Trigger

This MCP does exactly one thing: it triggers incidents in PagerDuty. That's its only function, and nothing else. Incredible for giving your AI agents the power to wake up engineers.

View Connector
Opsgenie logo
02 11 capabilities

Opsgenie

Automate incident management via Opsgenie. manage alerts, track on-calls, and coordinate incidents directly from any AI agent.

View Connector
Better Stack logo
03 10 capabilities

Better Stack

Automate incident management via Better Stack. monitor uptime, manage incidents, and control on-call schedules securely from your AI agent.

View Connector
SigNoz (Datadog Alternative) logo
04 5 capabilities

SigNoz (Datadog Alternative)

Monitor infrastructure and manage alert rules via SigNoz. list, create, and update observability alerts directly from your AI agent.

View Connector
Incident.io logo
05 10 capabilities

Incident.io

Manage incidents, roles, and on-call schedules via Incident.io API.

View Connector
Instatus (Status Pages API) logo
06 28 capabilities

Instatus (Status Pages API)

Automate your status pages via Instatus. manage incidents, update component statuses, and monitor system health directly from any AI agent.

View Connector

Bring your own AI

Change the model, client or framework. Keep PagerDuty connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about PagerDuty.

The practical details behind the request, access and result.

Can I use PagerDuty MCP to acknowledge alerts?

Yes, you can acknowledge, resolve, or escalate incidents directly through your AI client. This helps you manage the alert lifecycle without leaving your current workspace.

Does PagerDuty MCP show who is on-call?

Yes, you can see who is currently on-call across all your schedules. It's a fast way to find the right person to contact during an outage.

How do I connect PagerDuty to my AI agent?

You just need to subscribe to this Connector on Vinkius and add your PagerDuty REST API Key from your account settings. Once connected, your agent can access your data.

Can I see my escalation policies?

Yes, you can list all escalation policies to see how incidents route through your teams. This gives you a clear picture of your alert routing.

Is PagerDuty MCP good for SRE teams?

Yes, it's designed for SREs and DevOps teams who need to triage and resolve incidents quickly. It helps reduce the time spent on manual dashboard navigation.

Can I create new incidents with this?

Yes, you can create new incidents on specific services by providing the title and your user email. This makes it easy to log new issues as they arise.

Can I see my service configurations?

Yes, you can view the detailed configuration and health status of any monitored service. This is helpful for checking integrations and other settings.

Can I acknowledge and resolve incidents directly from my AI agent?

Yes! Use the update_incident capability with the incident ID and your PagerDuty email. Set status to acknowledged or resolved to change the incident state instantly without opening the PagerDuty dashboard.

How do I find out who is on-call right now?

Run the list_oncalls capability. It returns every user currently on-call across all schedules and escalation levels, showing their name, escalation policy, and coverage window.

Can I create incidents programmatically for testing or escalation?

Absolutely. Use create_incident with your PagerDuty email, the target service ID, a descriptive title, and optionally set urgency to high or low. The incident will immediately trigger according to the service's escalation policy.

One connection away

Give your agent a direct line to PagerDuty.

Connect PagerDuty once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available