Reports on open incidents and their alerts, declares and escalates new ones, maintains severities and roles, and keeps the service catalog current.
112actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro edits an existing incident in incident.io. Supporters can update incident status, severity, and metadata without accessing the incident dashboard.
Ayro creates an alert route in incident.io to direct notifications. Supporters can configure how alerts flow without manual setup overhead.
Ayro creates a new alert attribute in incident.io. Supporters can extend alert tagging without involving the incident management admin.
Each card is one request a support team gets, and the incident.io actions Ayro runs to close it.
Ayro opens the incident and reads the updates posted against it alongside the alerts that fed into it, so someone joining late gets the current picture instead of scrolling back through a channel.
Ayro creates the incident at the right severity, raises the escalation that pages a responder, and edits the record as the picture changes, so declaring is never the slowest step.
Ayro creates the severity a new class of incident needs, defines the response role that owns it, and updates the statuses an incident moves through, so the process stays the one your team designed.
Ayro adds a new service or team as a catalog entry, updates a batch of entries when ownership shifts, and extends the type schema when a field is missing, so an incident links to something real.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the incident.io actions it has and picks the ones a request needs.
Authorize the incident.io 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 incident.io 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 freeincident.io · Ayro
What can you do in incident.io 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 incident.io.
Yes. List Schedules V2 and List Schedule Entries V2 return the rotas and who covers each window, and List Escalation Paths V2 with Show Escalations V2 show where an unacknowledged page travels next, so Ayro can name the person rather than the team.
All 112 actions your agent can call on incident.io, straight from the live MCP connection.
Create an alert attribute in incident.io.
Create an alert route in incident.io.
Create a new alert source in incident.io.
Create a catalog entry in incident.io.
Create a catalog entry in incident.io using the V3 API.
Create a new catalog type in incident.io V3 API.
Create a new custom field option in incident.io.
Create a custom field in incident.io using the V2 API.
Create an escalation in incident.io.
Create a new incident role in incident.io.
Create a new incident role in incident.io using the V2 API.
Create a new incident status in incident.io.
Create a new incident in incident.io.
Create a new incident in incident.io using the V2 API.
Create a managed resource in incident.io.
Create a new severity level in incident.io.
Delete an alert attribute from incident.io.
Delete an alert route from incident.io.
Delete an alert source from incident.io.
Delete a catalog entry from incident.io.
Archive a catalog entry from incident.io using V3 API.
Delete a catalog type from incident.io.
Archive a catalog type and all its entries from incident.io.
Delete a custom field from incident.io.
Delete a custom field option in incident.io.
Delete a custom field from incident.io using the V2 API.
Delete an escalation path from incident.io.
Delete an incident role by ID.
Delete an incident role by ID.
Delete an incident status by its ID.
Same connection, same setup. Pick the next one your team already uses.
Opens tickets, creates projects and tasks, logs expenses, and reads the invoices, estimates, and timesheets behind a client question.
Starts and stops time tracking, reports an employee's hours and active project, and creates new projects from the conversation.
Logs hours to the right project, sends estimates from a scoping conversation, raises invoices and records payments, and sets new clients up to bill.
Logs time against the right project, reports budget and utilisation, raises and emails invoices from tracked hours, and chases what has gone unpaid.
Register cardholders and users, issue cards and pull the virtual card image, provision financial accounts and counterparties, and mint API keys.
Pulls the account's project list with assigned users, budgets, dates, and archived status, so project questions are answered from live data.

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