An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Pagerduty Incident Trigger to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Let your AI agent wake up your on-call engineers.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 1 capability

We ship only the actions that matter.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through PagerDuty Events.

  1. 01

    Trigger pagerduty incident

    This capability sends an incident directly to PagerDuty via the Events API V2. You provide a summary, the source, and a severity level like critical, error, warning, or info.

Real work

What teams actually run

01

Automated Error Escalation

An agent monitors application logs and triggers a PagerDuty incident when it sees a pattern of 500 errors.

02

Deployment Guardrails

During a canary deployment, the agent detects a performance dip and pages the on-call engineer to investigate.

03

Infrastructure Monitoring

The agent watches cloud resource usage and triggers an incident if a service becomes unresponsive.

04

Security Alerting

An agent identifies suspicious login patterns and immediately escalates the event to the security team.

Automate a task

Put PagerDuty Events to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

PagerDuty Events works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put PagerDuty Events to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

918ms average. Fast in production.

PagerDuty Events is checked daily against the live service.

Daily averagePeak 1176ms
Oct 5Today
Fastest day
708ms
Slowest day
1176ms
14-day trend
Improving-24%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of PagerDuty Events, so you can see the experience inside your AI.

It does not authenticate your account with PagerDuty Events. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

PagerDuty Events Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_kKI8TivX0k47Sbfm98eG7QAfs3djX089vGi7fwVA/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — PagerDuty Events capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "pagerduty-incident-trigger-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_kKI8TivX0k47Sbfm98eG7QAfs3djX089vGi7fwVA/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up PagerDuty Events in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work PagerDuty Events owners hand off.

This is for technical teams who want to close the loop between automated monitoring and human response.

  • 01

    SREs

    They hand off the task of monitoring complex system metrics to an agent that can page a human when thresholds are hit.

  • 02

    DevOps Engineers

    They use the agent to trigger alerts during deployment pipelines if errors are detected.

  • 03

    Platform Engineers

    They give their agents the ability to escalate infrastructure failures immediately.

FAQ

Questions PagerDuty Events owners ask.

  • 01

    Can this MCP read my PagerDuty schedules?

    No. This MCP only uses the Events API V2, which is a one-way street for sending alerts. It cannot read your incident history or modify your on-call rotations.

  • 02

    What information do I need to provide to trigger an incident?

    You need to provide a summary of the issue and the source. You can also specify a severity level, which defaults to critical if you don't choose one.

  • 03

    Is this a full PagerDuty integration?

    No. This is a specialized MCP designed specifically to trigger incidents. It does not manage tickets or query the REST API for existing data.

  • 04

    Which AI clients can use this MCP?

    Any MCP-compatible client like Claude, Cursor, or Windsurf can use this capability once connected through Vinkius.

  • 05

    How secure is the connection?

    It is highly secure because it relies on a single Integration Key and does not require broad API permissions or complex OAuth setups.

  • 06

    Can the agent resolve PagerDuty incidents with this?

    No. This MCP 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.

  • 07

    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.

Explore

More in Industry Titans

Suggestions

Connect PagerDuty Events to Claude, Cursor, ChatGPT & more