PagerDuty Incident Trigger MCP Server with 1 Tools for Claude, Cursor, and AI Agents
GDPR Free for SubscribersThis 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. Vinkius routes your AI agents directly to PagerDuty Incident Trigger through a governed connection. 1 tools ready to use with Claude, ChatGPT, Cursor, or any AI agent — no hosting, no setup, connect in 30 seconds.
Ask AI about this server
Compatible with every major AI agent and IDE
Gemini* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
What is the PagerDuty Events MCP Server?
The PagerDuty Events MCP Server routes AI agents like Claude, ChatGPT, and Cursor directly to PagerDuty Events via 1 tools. 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. Powered by Vinkius — your credentials stay on your side of the connection, every request is auditable. Connect in under 2 minutes.
Built-in capabilities (1)
Tools for your AI Agents to operate PagerDuty Events
Ask your AI agent "Trigger a critical PagerDuty incident for the payment-gateway saying transactions are failing." and get the answer without opening a single dashboard. With 1 tools connected to real PagerDuty Events data, your agents reason over live information, cross-reference it with other MCP servers, and deliver insights you would spend hours assembling manually.
Works with Claude, ChatGPT, Cursor, and any MCP-compatible client. Powered by Vinkius — your credentials never touch the AI model, every request is auditable. Connect in under two minutes.
Why teams choose Vinkius
One subscription gives you the infrastructure to connect your AI agents to thousands of MCP servers — and deploy your own to the Vinkius Edge. Your credentials stay yours. Your data flows directly between your agent and the API. DLP blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade routing and governance, zero maintenance.
Build your own MCP Server with our secure development framework →The PagerDuty Incident Trigger App Connector works with every AI agent you already use
…and any MCP-compatible client
Use all 1 PagerDuty Incident Trigger tools with your AI agents right now
Vinkius routes your AI agents to PagerDuty Incident Trigger through a governed proxy. Beyond a simple connection, you get full visibility into every action your agents perform, with enterprise-grade security and up to 60% savings on AI costs.
Trigger pagerduty incident on PagerDuty Incident Trigger
Provide a clear summary, the source of the issue, and an optional severity level ("critical", "error", "warning", "info"). Defaults to critical. Trigger an incident in PagerDuty using the Events API V2
What the PagerDuty Incident Trigger MCP Server unlocks
We refused to build a bloated incident management integration that attempts to manage on-call schedules, resolve tickets, or query PagerDuty REST APIs. Instead, this MCP server provides a surgical, zero-trust bridge: just triggering incidents via the Events API V2.
Your AI agent gains the immediate, zero-friction ability to evaluate anomalies and instantly escalate critical issues directly to the on-call engineer's phone.
The Superpowers
- Instant Escalation: Give your agent the authority to declare a 'Critical' state. The agent provides a summary, source, and severity, and PagerDuty handles the paging.
- Zero-Bloat Integration: No massive SDKs or complex OAuth flows. Just a single Integration Key (Routing Key) is required to push events.
- Absolute Containment: Because this uses the one-way Events API V2, the agent cannot read your incident history, cannot modify on-call schedules, and cannot snoop on resolving engineers. It is the purest, safest way to give your AI paging superpowers.
Frequently asked questions about the PagerDuty Incident Trigger MCP Server
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.
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.
More in this category
Odoo ERP (Full)
7 toolsManage CRM leads, contacts, companies, sales orders, and notes — complete Odoo ERP access through natural conversation.
Oracle NetSuite
9 toolsManage financials, sales orders, inventory, and customer records on Oracle NetSuite — the leading cloud ERP.
Automate Reddit interactions via AI — search subreddits, list hot posts, and retrieve comment threads directly.
Riot Games
12 toolsAccess League of Legends player data — summoner profiles, match history, ranked stats, champion masteries and live games.
You might also like
Nominatim
5 toolsGeocode addresses, reverse geocode coordinates and explore OpenStreetMap data — no API key required.
Honeycomb
12 toolsAutomate observability via Honeycomb — manage datasets, queries, and markers directly from any AI agent.
Open Food Facts
2 toolsScan barcodes and search packaged food products for complete nutritional data, Nutri-Score grades, allergens, and ingredient analysis.
MLflow (ML Lifecycle Management)
6 toolsManage ML lifecycle via MLflow — track training runs, monitor metrics, and audit the model registry.
We built the connector to PagerDuty Incident Trigger. Now put your agents to work. Fully governed.
Vinkius is the AI Gateway with managed hosting. Stop building connectors. Every connection runs inside eight layers of security.
Hosted, sandboxed, and live on AWS. You don't provision anything. You don't maintain anything. You connect.
Every tool call, every token, every response. Logged and auditable. Data flows direct from PagerDuty Incident Trigger to your agent. Nothing is stored on our side. Ever.
Eight governance layers on every request. Sensitive data redacted before it reaches the model. Kill switch if anything goes sideways. Always on.