Skip to content
Vinkius

PagerDuty Events Connector for AI agents.

1 live capability

Let your AI agent automatically escalate critical production issues to on-call engineers.

Live agent request PagerDuty Events / Connector

Waiting for input…

AI Agent

Why people use PagerDuty Events

PagerDuty Incident Trigger for Reducing Manual Alerting Fatigue

With this Connector, your AI agent handles the triage. It sees the error, summarizes the logs, and fires off the PagerDuty incident automatically. You get a notification on your phone with the right context, skipping the manual overhead entirely.

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

What Vinkius changes

Your agent gets a direct line to your on-call rotation without any unnecessary permissions.

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

One account · 5,900+ Connectors

  1. Real-world use case 01

    Payment Gateway Failure

    An AI agent monitoring Stripe logs sees a 50% drop in successful transactions and uses trigger_pagerduty_incident to wake up the billing team.

  2. Real-world use case 02

    Database Latency Spike

    A monitoring agent detects slow queries and triggers a 'Warning' incident to let the DBA know before the site goes down.

  3. Real-world use case 03

    Security Breach Detection

    A security agent identifies an unauthorized login attempt and immediately pushes a 'Critical' alert to the security operations center.

Complete set · 1capability

The complete PagerDuty Events capability set.

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

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through PagerDuty Events.

  1. 01 Capability

    Trigger pagerduty incident

    Sends a new incident to PagerDuty with a summary, source, and severity level. It uses the Events API V2 to ensure your agent only has permission to push alerts.

Set up in minutes

One URL. Then ask PagerDuty Events to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use PagerDuty Events 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_kKI8TivX0k47Sbfm98eG7QAfs3djX089vGi7fwVA/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 Events, and paste the URL above.

  3. Step 03

    Turn it on in chat

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

Where the request belongs

Work PagerDuty Events can move forward.

Built around the request

This is for the SRE or DevOps engineer who is tired of manually triaging logs at 3 AM and wants an AI that can actually take action when things go sideways.

01

Site Reliability Engineer

Automating the human-in-the-loop part of incident detection to reduce mean time to acknowledge.

02

DevOps Engineer

Creating automated failover alerts that actually reach the right phone without manual copy-pasting.

03

Incident Response Manager

Ensuring critical spikes get escalated to the correct team automatically.

Bring your own AI

Change the model, client or framework. Keep PagerDuty Events 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 Events.

The practical details behind the request, access and result.

Can the PagerDuty Incident Trigger MCP read my current on-call schedule?

No, this Connector is strictly one-way. It can only send new incidents to PagerDuty and cannot see who is currently on call or read any existing data.

How do I give my AI agent permission to trigger alerts?

You just need a single PagerDuty Routing Key. You add this to the Connector configuration, and your agent can start pushing alerts immediately.

Will this Connector create a new ticket every time it's called?

Yes, every time your agent calls trigger_pagerduty_incident, a new incident is created in PagerDuty based on the summary and severity you provide.

Is it safe to let an AI agent trigger PagerDuty incidents?

Yes, because this Connector uses the Events API V2. It doesn't have permissions to read, modify, or delete anything in your PagerDuty account.

Can I set the severity of the incident?

Yes, you can specify whether the alert is critical, an error, a warning, or info. It defaults to critical if you don't specify one.

Does this work with Claude and Cursor?

Yes, any MCP-compatible client like Claude, Cursor, or Windsurf can use this to interact with PagerDuty.

Can the agent resolve PagerDuty incidents with this?

No. This Connector exclusively uses the 'trigger' event action. It cannot resolve or acknowledge incidents. Its sole purpose is to wake up human operators when it detects a critical anomaly.

How do I get a PagerDuty Integration Key?

In PagerDuty, go to Services > Service Directory. Select your service, go to the Integrations tab, and add a new 'Events API V2' integration. Copy the resulting Integration Key.

One connection away

Give your agent a direct line to PagerDuty Events.

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

Explore every Connector No credit card required · Free tier available