PagerDuty for your agents.
Connect PagerDuty once and every agent you run inside Even (Claude Code, Codex, OpenCode, Even Agents) can use it: 10 curated tools, discovered on demand, with your key stored on your machine and every call going direct to PagerDuty.
What agents can do with PagerDuty
Curated for agents: the calls that matter, with schemas and descriptions written for tool use, not an endpoint dump.
pagerduty_list_incidentsList incidents with optional status filter.
pagerduty_get_incidentGet a single incident by id.
pagerduty_list_usersList users on the account.
pagerduty_get_on_callList the current on-call entries for all schedules.
pagerduty_list_servicesList services.
pagerduty_get_serviceGet details of a single service by id.
pagerduty_list_escalation_policiesList escalation policies.
pagerduty_list_schedulesList on-call schedules.
pagerduty_list_teamsList teams on the account.
pagerduty_create_incident_noteAdd a note to an incident.
Connect it in a minute
The connect flow is agent-driven: Even opens the key page in its own browser and collects the key through a secure native field. It never passes through the chat.
- Paste the prompt below into any agent running inside Even, or click Connect in Even's catalog.
- Go to PagerDuty Console > Integrations > API Access Keys.
- Click 'Create New API Key', give it a description.
- Select 'Full Access' (read-only if you prefer).
- Copy the key; it is shown once.
- Paste the key into Even's secure field. Even verifies it and your agents are live.
Connect PagerDuty to Even: call connect_begin("pagerduty") on the even-connect MCP and walk me through it.
List incidents by status, retrieve on-call schedules for coverage, and list all services in account.
More Even Connect services
One MCP server, a handful of meta-tools, every service below. Agents search for the right tool at run time, so context stays lean.