Sauce Error Reporting MCP server is now live in open Beta, letting you query your crash and error data from an AI agent instead of the dashboard.
What is Changing?
Previously, investigating an error meant building the view by hand in the Error Reporting UI. With the MCP server, an AI agent can access this data directly and integrate into your engineering workflows to speed up debugging and fixing production errors.
List your projects: See everything in your org without leaving your agent.
Discover indexed attributes: Including your project's custom attributes, so you stop guessing at field names.
Search, query, and group errors : Triage without constructing the view yourself.
Fetch a single error in full: Get stacktrace, attributes, and attachments in one call.
Read-only by design: The server only reads your error data. It never writes, edits, or deletes.
Why this Matters
Seamless triage: Triage happens where you already are, instead of context-switching into a separate dashboard.
Smart discovery: Attribute discovery removes the guesswork that slows down querying unfamiliar projects.
Rapid resolution: Move faster from error to root cause, the investigation happens in one place, next to the code that threw it.
Getting Started
Connect using your existing Error Reporting SSO credentials: no separate setup required.
We Want Your Feedback
This capability is currently in Beta, and your input will help us make it better. If something isn't working as expected, please let us know, here's how:
Use the feedback tool built into the MCP.
Reach out to us directly at neerav.mittal@saucelabs.com or you can also share feedback with your CSM.
Answer the short survey coming your way to share your experience.
Not using Error Reporting for crash and error monitoring yet?