The use case: how Exa deploys Sentry
Exa uses Sentry error monitoring on its Node.js production layer, including the customer-facing API gateway, with alerts delivered through Slack. Using Sentry's MCP server, issue context is routed to coding agents that open pull requests for human review.
In the customer’s words
If it's urgent, we just say to the coding agent, 'can you look at this and can you fix it?' It has all the MCPs and connectivity to Sentry, gets all the context around the error and the codebase, and fixes it from there.Other AI tools used by Exa
Other public relationships recorded on usedby.
Explore Exa’s AI stack
Sentry users in Artificial Intelligence
Companies in the same sector, with public evidence.
See all Sentry customers
Go straight to the source
Based on Sentry’s published case study. We check the public evidence; the results are reported by the vendor.
sentry.io- Last checked
- Nov 12, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Exa.
- Exa uses SentryChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Using Sentry's MCP server, Exa routes issue context (stack traces, breadcrumbs, affected users) to coding agents, which open pull requests for human review. This workflow runs on a daily cadence even without an active incident.