Gleap AI agents can use Sentry through Composio, for engineering teams that track errors in Sentry and receive bug reports from customers in Gleap. With Sentry connected, Kai Code and Kai Support can read the error, stack trace and release behind a report, and a custom agent can look up issues for your team.
What a Gleap agent can do in Sentry
- The error behind a bug report: the actions List an organization’s issues and Fetch issue event by id find the Sentry issue and stack trace that match a Gleap report’s time, page and browser.
- Evidence during an investigation: Kai Support’s investigation can use the MCP servers enabled in Kai Code’s settings, so it can check Sentry while it traces the code for a report.
- A stack trace for the fix: Kai Code can read the Sentry event while it prepares a pull request, and your engineers review and merge it.
- Which release introduced it: List organization releases and Retrieve release commits show when the error first appeared and which commits shipped with it.
- How widespread it is: Get project event stats and Fetch Tag Values for Issue show event counts and the browsers or versions affected.
Example: a checkout button that does nothing
A customer reports through the Gleap widget that the checkout button does nothing. Kai Support investigates the ticket, finds a matching TypeError in Sentry from the same page and browser, traces it to the code and prepares a coding task. Kai Code starts the task on its own when you allow it, or a teammate does, and reads the stack trace while it prepares the pull request. Your engineers review and merge it, and a teammate confirms the fix is live before the customer hears back.
How to connect Sentry
- In Gleap, open Kai Code, click Settings and open MCP.
- Click Add MCP server, search for “Sentry” and select it.
- Click Connect Sentry and approve access in the Sentry sign-in window.
- Open the Sentry server and switch off the tools Kai Code should not call, such as Delete organization issue, Bulk remove an organization’s issues and the release changes.
- For a custom agent, add Sentry under the agent’s Tools with Add tool instead, then publish and test it.
Kai Code is on Team, Pro and Enterprise, and Kai Support can use connected apps as tools on the same plans. Custom agents are on the Team, Pro and Enterprise plans.
FAQ
Does Gleap integrate with Sentry?
Yes. Kai Code, Kai Support and custom agents use Sentry through Composio’s Sentry toolkit, connected with a Sentry sign-in. They read or change Sentry data only while they run; Gleap does not import Sentry issues or sync them with tickets.
Does Gleap connect to Sentry through MCP?
Yes. Gleap connects to Composio’s MCP server for Sentry with the Sentry account you connect, and the agent calls only the actions you leave switched on. To use a different remote MCP server, add it by URL: as a Custom MCP tool for Kai Support or a custom agent, or as a custom HTTP server in Kai Code.
What can a Gleap AI agent do in Sentry?
It can list and read issues, events, tags, releases, commits and deploys, update issue status and attributes, link external issues, and delete issues or releases. For investigation and fixes, switch the delete and bulk actions off.
Which Gleap plan includes the Sentry integration?
Kai Code and Kai Support’s investigations can use Sentry on Team, Pro and Enterprise, and Kai Support can use connected apps as tools in its customer conversations on the same plans. Custom agents that use Sentry are part of the Team, Pro and Enterprise plans. Your Sentry plan and the connected user’s permissions decide which projects and data the agents see. AI usage is billed separately; see pricing.
Does Gleap replace Sentry?
No. Sentry records errors in your code; Gleap collects reports from the people using your product, with the steps, screenshot and environment they saw. Connecting the two lets the agents match a customer’s report to the error Sentry recorded.
