AI agent for PagerDuty
Connect PagerDuty to your AI agent through the WorkAist MCP server.
The WorkAist PagerDuty connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write PagerDuty data — monitoring, error tracking — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.
Authentication & setup
The PagerDuty connector authenticates via OAuth 2.0.
WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.
Frequently paired with PagerDuty
FAQ
Can a WorkAist AI agent really automate PagerDuty end-to-end?▼
Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.
How does this differ from using the PagerDuty API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents PagerDuty as part of a unified Knowledge Graph alongside your other tools.
What does it cost?▼
WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for PagerDuty's own API costs (if any) and the LLM tokens your agent consumes.
Is my PagerDuty data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from PagerDuty → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if PagerDuty changes its API?▼
The connector is versioned and published openly. When PagerDuty ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.