Can Lyro read our existing errors out of Honeybadger?

No. Every action in this toolkit writes into Honeybadger - check-ins, deployments, exceptions, events, and source-map uploads. Fetching a fault list, resolving an error, or changing project settings all stay in the Honeybadger interface.

How much data can travel with a check-in?

Report Check-In With Payload carries up to 20KB of metrics, status, or metadata alongside the ping, which is enough for the row counts or durations that make a green check-in meaningful. Larger or free-form telemetry belongs in Report Event, which is sent as newline-delimited JSON and returns a tracking ID per event.

Does reporting a deployment change anything about existing errors?

It can. Honeybadger uses deployment reports to correlate errors with releases and to automatically resolve errors when you deploy to an environment, which is why environment and revision are worth sending even though every deployment field is optional.

What does a source-map upload actually need?

Three things, associated with the production URL of the asset: the minified JavaScript file, its corresponding .map file, and optionally the original sources the map references. Upload File to S3 is the staging step for preparing those files before the source-map upload itself.

Honeybadger MCP integration

Reports check-ins, deployments, exceptions, and custom events into Honeybadger, and uploads the source maps behind readable stack traces.

Connect Honeybadger See all integrations

7actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Upload source map
Lyro uploads source maps to Honeybadger to make error messages readable to support teams. Debugging becomes easier because code errors show line numbers instead of minified gibberish.
Report event
Lyro reports custom events to Honeybadger Insights for tracking customer interactions and support metrics. Teams see real-time visibility into key moments without manual logging.
Report exception
Lyro reports exceptions to Honeybadger when errors occur during customer conversations. Errors surface immediately for triage instead of being missed in logs.

See all 7 actions

How businesses use Honeybadger + Lyro

Each card is one request a support team gets, and the Honeybadger actions Lyro runs to close it.

Prove a scheduled job actually finished
Lyro pings Honeybadger at the end of a successful run, so a cron job or background process that stops silently triggers an alert instead of going unnoticed until someone asks.
Report Check-InReport Check-In With PayloadReport Event
Tie an error back to the release that caused it
Reporting the deployment with its environment and revision puts it on the project's Deployments page, so new errors line up against the release they arrived with.
Report DeploymentReport EventReport Exception
Send an exception with the context around it
A stack trace and its surrounding context go to Honeybadger as a notice, and any structured events - logins, feature usage, timing data - go to Insights alongside it.
Report ExceptionReport EventReport Check-In With Payload
Make minified stack traces readable again
Lyro uploads the minified JavaScript file, its .map, and any referenced sources against the production URL, so a trace shows real file names, functions, and line numbers.
Upload Source MapUpload File to S3Report Deployment

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 Honeybadger actions it has and picks the ones a request needs.

01
Connect Honeybadger
Authorize the Honeybadger 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 Honeybadger 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

Honeybadger · Lyro

Everything else about Honeybadger

Setup, permissions, and the limits of what Lyro can do inside Honeybadger.

No. Every action in this toolkit writes into Honeybadger - check-ins, deployments, exceptions, events, and source-map uploads. Fetching a fault list, resolving an error, or changing project settings all stay in the Honeybadger interface.

Every action available in Honeybadger

All 7 actions your agent can call on Honeybadger, straight from the live MCP connection.

Report check-in
Reports a check-in (ping) to Honeybadger for uptime monitoring.
Report check-in with payload
Report a check-in with additional payload data to Honeybadger.
Report deployment
Report a new deployment to Honeybadger for deployment tracking and error correlation.
Report event
Send custom events to Honeybadger Insights for tracking, monitoring, and analytics.
Report exception
Report an exception notice to Honeybadger.
Upload file to s3
Upload a local file to a managed S3 bucket.
Upload source map
Upload JavaScript source maps to Honeybadger for error stack trace de-minification.