incident.io MCP integration
Reports on open incidents and their alerts, declares and escalates new ones, maintains severities and roles, and keeps the service catalog current.
112actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Edit incident v2
Lyro edits an existing incident in incident.io. Supporters can update incident status, severity, and metadata without accessing the incident dashboard.
Create alert route v2
Lyro creates an alert route in incident.io to direct notifications. Supporters can configure how alerts flow without manual setup overhead.
Create alert attribute v2
Lyro creates a new alert attribute in incident.io. Supporters can extend alert tagging without involving the incident management admin.
How businesses use incident.io + Lyro
Each card is one request a support team gets, and the incident.io actions Lyro runs to close it.
Say what is actually happening on an incident
Lyro 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.
Get Incident by ID (V2)List Incident Updates V2List Incident Alerts V2Declare an incident and get someone on it
Lyro 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.
Create Incident V2Create Escalation V2Edit Incident V2Keep severities and roles matching how you work
Lyro 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.
Create SeverityCreate Incident Role V2Update Incident StatusKeep the catalog behind incidents accurate
Lyro 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.
Create Catalog Entry V3Bulk Update Catalog Entries V3Update Catalog Type Schema V3
How it works
Get started in 3 steps
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the incident.io actions it has and picks the ones a request needs.
- 01
Connect incident.io
Authorize the incident.io account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
- 02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the incident.io actions that close it and chains as many as the request needs.
- 03
Watch it work
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 free
Everything else about incident.io
Setup, permissions, and the limits of what Lyro 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 Lyro can name the person rather than the team.
Every action available in incident.io
All 112 actions your agent can call on incident.io, straight from the live MCP connection.
Create alert attribute v2
Create an alert attribute in incident.io.
Create alert route v2
Create an alert route in incident.io.
Create alert source v2
Create a new alert source in incident.io.
Create catalog entry v2
Create a catalog entry in incident.io.
Create catalog entry v3
Create a catalog entry in incident.io using the V3 API.
Create catalog type v3
Create a new catalog type in incident.io V3 API.
Create custom field option
Create a new custom field option in incident.io.
Create custom field v2
Create a custom field in incident.io using the V2 API.
Create escalation v2
Create an escalation in incident.io.
Create incident role
Create a new incident role in incident.io.
Create incident role v2
Create a new incident role in incident.io using the V2 API.
Create incident status
Create a new incident status in incident.io.
Create incident v1
Create a new incident in incident.io.
Create incident v2
Create a new incident in incident.io using the V2 API.
Create managed resource v2
Create a managed resource in incident.io.
Create severity
Create a new severity level in incident.io.
Delete alert attribute v2
Delete an alert attribute from incident.io.
Delete alert route v2
Delete an alert route from incident.io.
Delete alert source v2
Delete an alert source from incident.io.
Delete catalog entry v2
Delete a catalog entry from incident.io.
Delete catalog entry v3
Archive a catalog entry from incident.io using V3 API.
Delete catalog type v2
Delete a catalog type from incident.io.
Delete catalog type v3
Archive a catalog type and all its entries from incident.io.
Delete custom field
Delete a custom field from incident.io.
Delete custom field option
Delete a custom field option in incident.io.
Delete custom field v2
Delete a custom field from incident.io using the V2 API.
Delete escalation path v2
Delete an escalation path from incident.io.
Delete incident role v2
Delete an incident role by ID.
Delete incident role v1
Delete an incident role by ID.
Delete incident status v1
Delete an incident status by its ID.
The tools incident.io sits next to
Same connection, same setup. Pick the next one your team already uses.
Agiled
Opens tickets, creates projects and tasks, logs expenses, and reads the invoices, estimates, and timesheets behind a client question.
Desktime
Starts and stops time tracking, reports an employee's hours and active project, and creates new projects from the conversation.
Harvest
Logs hours to the right project, sends estimates from a scoping conversation, raises invoices and records payments, and sets new clients up to bill.
Moco
Logs time against the right project, reports budget and utilisation, raises and emails invoices from tracked hours, and chases what has gone unpaid.
Rize
Register cardholders and users, issue cards and pull the virtual card image, provision financial accounts and counterparties, and mint API keys.
Timecamp
Pulls the account's project list with assigned users, budgets, dates, and archived status, so project questions are answered from live data.
Ready to connect incident.io?
Authorize the account and your agent has all 112 actions from the first conversation.