Better stack MCP integration
Checks whether a service is actually up, acknowledges and escalates open incidents, publishes status page updates, and maintains the on-call rota.
117actions available
Three actions you can hand over today
Every action runs live through MCP. Nothing to build, nothing to maintain.
Create incident comment
Lyro adds notes to an ongoing incident in Better Stack during support conversations with customers. On-call teams stay informed without context-switching to a separate incident platform.
Escalate incident
Lyro escalates a critical outage to the right team or on-call engineer within seconds. Response times shrink because escalations reach people immediately instead of waiting for ticket triage.
Resolve incident
Lyro marks an incident resolved in Better Stack once the customer confirms the problem is fixed. Status updates propagate instantly, so follow-up work and post-mortems start right away.
How businesses use Better stack + Lyro
Each card is one request a support team gets, and the Better stack actions Lyro runs to close it.
Say whether a service is actually up
Lyro opens the monitor behind the service in question, reads its availability over the period being asked about, and checks response times, so a customer reporting a problem is told what the checks show.
Get MonitorGet Monitor AvailabilityGet Monitor Response TimesWork an incident from acknowledge to resolve
Lyro acknowledges the open incident so responders know it is seen, escalates it when nobody picks it up, and resolves it once the checks recover, leaving a comment at each step.
Acknowledge IncidentEscalate IncidentResolve IncidentTell customers what is happening
Lyro publishes the status page report, posts each update as the picture changes, and switches the affected resource's state, so customers stop asking whether anyone has noticed yet.
Create Status Page ReportCreate Status UpdateUpdate Status Page ResourceKeep the on-call rota and its policies current
Lyro creates or updates the on-call schedule, adjusts the escalation policy behind it, and reads the upcoming rota events, so the person paged at three in the morning is the one who should be.
Create On-Call ScheduleUpdate Escalation PolicyList On-Call Schedule Events
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 Better stack actions it has and picks the ones a request needs.
- 01
Connect Better stack
Authorize the Better stack 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 Better stack 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 Better stack
Setup, permissions, and the limits of what Lyro can do inside Better stack.
A monitor checks a service from the outside, a heartbeat waits for a job to check in. Create Heartbeat, Get Heartbeat Availability, and List Heartbeats cover the second kind, so Lyro can flag that a nightly job silently stopped running, which a URL uptime check would never notice.
Every action available in Better stack
All 117 actions your agent can call on Better stack, straight from the live MCP connection.
Acknowledge incident
Acknowledge an ongoing incident.
Create escalation policy
Creates a new escalation policy for incident management.
Create heartbeat
Create a new heartbeat monitor for cron jobs and scheduled tasks.
Create heartbeat group
Create a new heartbeat group.
Create incident
Create a new incident and alert the on-call person.
Create incident comment
Create a new comment on an incident.
Create metadata
Create or update a metadata record for a resource.
Create monitor
Create a new uptime monitor for a URL or service.
Create monitor group
Create a new monitor group.
Create on-call schedule
Create a new on-call schedule.
Create outgoing webhook integration
Create a new outgoing webhook integration.
Create escalation policy group
Create a new escalation policy group.
Create source group
Create a new source group.
Create status page group
Create a new status page group.
Create status page report
Create a new status page report (incident or maintenance).
Create status page resource
Create a new status page resource.
Create status page section
Create a new section on a status page.
Create status update
Create a new status update for an existing status report.
Create severity level
Create a new severity level (urgency) for incident management.
Create urgency group
Create a new urgency group (severity group) for incident categorization.
Delete escalation policy
Delete an escalation policy by ID.
Delete heartbeat
Permanently delete a heartbeat by ID.
Delete heartbeat group
Permanently delete a heartbeat group by ID.
Delete incident
Permanently delete an existing incident by ID.
Delete incident comment
Delete an existing comment from an incident.
Delete monitor
Permanently delete a monitor by ID from Better Stack Uptime.
Delete monitor group
Permanently delete a monitor group by ID from Better Stack Uptime.
Delete on-call schedule
Permanently delete an on-call schedule by ID.
Delete outgoing webhook integration
Delete an outgoing webhook integration by ID.
Delete escalation policy group
Delete an escalation policy group by ID.
The tools Better stack sits next to
Same connection, same setup. Pick the next one your team already uses.
Appveyor
Resolves builds by version, quotes job logs and artifacts, surfaces status badges, and answers who has access to the account.
Codeinterpreter
Spins up a Python sandbox, uploads files into it, runs code or shell commands, and returns the file that comes out.
Emailable
Verifies an address the moment it is given, pushes a full list through as one batch, and follows the job until its results are ready.
Mailboxlayer
Validates an email address on the spot - syntax, domain, and SMTP - right inside the conversation.
Rocketadmin
Finds the right table, reads a row by primary key or filter, writes the correction back, and exports a filtered table as CSV.
Truvera
Verifies submitted credentials and presentations, resolves DID documents, and provisions the API keys and webhooks around them.
Ready to connect Better stack?
Authorize the account and your agent has all 117 actions from the first conversation.