Compatible with every major AI agent and IDE
What is the PagerDuty Incident Trigger MCP Server?
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.
Built-in capabilities (1)
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
Why Windsurf?
Windsurf's Cascade agent chains multiple PagerDuty Incident Trigger tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 1 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 1 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
PagerDuty Incident Trigger in Windsurf
PagerDuty Incident Trigger and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect PagerDuty Incident Trigger to Windsurf through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for PagerDuty Incident Trigger in Windsurf
The PagerDuty Incident Trigger 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. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Windsurf only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
PagerDuty Incident Trigger for Windsurf
Every tool call from Windsurf to the PagerDuty Incident Trigger MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
How does Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.
Explore More MCP Servers
View all →
Funil de Vendas
12 toolsManage CRM opportunities, sales funnels, and activities via Funil de Vendas directly from your AI agent.

RenderMe
12 toolsAutomate video generation via RenderMe (re.video) templates directly from your AI agent.

QuickReply.ai Alternative
5 toolsAutomate WhatsApp marketing and customer engagement via QuickReply.ai — trigger journeys, send templates, and manage session messages directly from your AI agent.

Manatal
10 toolsManatal AI Recruitment and ATS platform to manage candidates, jobs, and applications.
