Reports who is on call, opens incidents and posts status updates, merges duplicates, and pages responders through a response play.
363actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves contact methods for a PagerDuty user to reach them during an incident. Teams reach the right person immediately instead of searching contact lists.
Ayro updates an existing change event in PagerDuty to reflect completed actions or status changes. Teams keep incident records current without manual PagerDuty navigation.
Ayro adds a service to an incident workflow trigger so that service's incidents automatically invoke the workflow. Teams ensure critical services follow response procedures without manual setup on each incident.
Each card is one request a support team gets, and the Pagerduty actions Ayro runs to close it.
Ayro reads the live on-call list and the schedule behind it, so the question of who to wake up is answered from PagerDuty rather than from a rota someone pasted into a channel last quarter.
Ayro files the incident against the right service, attaches the reporter's own account of what happened as a note, and posts the first status update so subscribers are informed immediately.
Ayro checks what is already open for the same service, folds duplicate reports into the incident of record, and snoozes the noise, so responders see one thread instead of a pile.
Ayro runs the response play attached to the service, requests the specific responders it names, and puts a schedule override in place when the person on call cannot take it.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Pagerduty actions it has and picks the ones a request needs.
Authorize the Pagerduty account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Pagerduty actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freePagerduty · Ayro
What can you do in Pagerduty without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Pagerduty.
It follows the actions you want in reach. Retrieve oncall list, Get schedules, and Fetch incident list are read-only calls. Create incident record, Post incident status update, and Create schedule overrides configuration write to PagerDuty, so a read-scoped connection will not be able to make them.
All 363 actions your agent can call on Pagerduty, straight from the live MCP connection.
Adds a service to an existing incident workflow trigger in PagerDuty, enabling the trigger to fire for incidents on that service.
This endpoint analyzes and aggregates incident metrics across all escalation policies in PagerDuty.
Retrieves and aggregates metrics for incidents across all services in PagerDuty.
Associates multiple service dependencies in PagerDuty, allowing you to define relationships between supporting and dependent services.
This endpoint associates a specific team with an automation action in PagerDuty.
Retrieves the audit records for a specific escalation policy in PagerDuty.
Converts a service's Event Rules to Event Orchestration rules.
Retrieves the count of paused incident reports in the PagerDuty system.
Create a Custom Field for an Incident Type.
Creates a new field option for a custom field on an incident type.
Creates a new custom field for incidents in PagerDuty.
Create a new incident type.
Creates a new Ruleset in PagerDuty for managing incident routing and notification rules.
Creates a new incident workflow trigger in PagerDuty.
Creates a new Runbook Automation runner in PagerDuty's Automation Actions.
This endpoint creates a new Business Service in PagerDuty, which represents a specific service or application that can be monitored and managed within the incident management platform.
Creates a new escalation policy in PagerDuty, defining how incidents are escalated to different responders or teams.
Creates a new Event Orchestration in PagerDuty, which defines how incoming events are processed and routed to appropriate services.
Creates a new Event Rule within a specified Ruleset in PagerDuty's incident management system.
Creates a new extension in PagerDuty, allowing for additional functionality or integrations to be added to your services.
Creates a new on-call handoff notification rule for a specific user in PagerDuty.
Creates a new field option for a specific custom field in PagerDuty's incident management system.
Creates a new incident in PagerDuty with specified details and assignments.
This endpoint creates a new Incident Workflow in PagerDuty, allowing users to define a series of automated steps to be executed during incident response.
Creates a new instance of an incident workflow for a specific incident in PagerDuty.
Creates a new integration for an existing event orchestration in PagerDuty.
Creates a new integration for a PagerDuty service to enable incident creation from external monitoring tools and systems.
Creates a new maintenance window in PagerDuty, allowing you to schedule periods of planned maintenance for specific services.
Creates a new on-call schedule in PagerDuty with one or more rotation layers.
Creates a new service in PagerDuty, which is a key component for managing incidents and alerts.
Same connection, same setup. Pick the next one your team already uses.
Triggers builds through Git webhooks, reports what shipped and to whom, and serves Enterprise App Store in-app updates.
Finds, creates, and updates DNS records, reports a zone's firewall and bot settings, and maps tunnels, pools, and account roles.
Reads secret values from the right config, generates end-to-end encrypted share links, rotates and annotates values, and answers who changed what.
Validates API credentials, returns the real device-enrollment steps with Connect key guidance, and permanently removes a custom role by ID.
Pulls the runtime logs behind a failing deploy, reports environment status, changes build and deploy settings, and audits tokens and integrations.
Traces a webhook through its delivery attempts, registers applications and endpoints, replays what failed, and rotates endpoint signing secrets.

Authorize the account and your agent has all 363 actions from the first conversation.
