Integration · Research and analyze

Sentry and Meteor AI agents

Connect Sentry to a WhatsApp Met: search issues and errors, open the details, assign or resolve and review sessions with Sentry's official MCP.

Book a demo See every integration

How does Sentry connect to Meteor?

With the Sentry ready connector, your Met uses Sentry's official MCP server with the account the admin authorizes. It searches issues, errors, logs, traces, metrics, profiles and session replays with natural language questions, opens an issue or a trace from its link, and changes an issue's status or assignee. It also asks Seer, Sentry's analysis, for the cause of an error. That way, when a customer writes that the app is failing, the Met finds the error and assigns it to the team. Changing issues and the catalog gateway start turned off because Sentry marks them as destructive; the admin decides whether to turn them on.

What it automates

What a Meteor Met does with Sentry

Find the error a customer reports

When a customer writes on WhatsApp that the app or the store is failing, the Met searches Sentry for unresolved issues from the last hours that match what they describe.

Explain an alert from its link

If the owner forwards the Met the link to a Sentry alert, the Met opens the issue and explains in plain words what is failing and since when.

Assign the problem to the team

If the admin turns on the action to change issues, which starts turned off, the Met assigns the issue to the person or team its instructions name, or marks it as resolved when the team confirms the fix.

Count how many times it happened

If the owner asks how many errors there were today or which ones are most common this week, the Met searches the error events and answers with the count.

15 tools

Everything your Met can ask Sentry for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`find_organizations`	Finds the Sentry organizations the account can access, up to 25 per page.
`find_projects`	Finds the projects in a Sentry organization, up to 25 per page.
`search_issues`	Searches grouped issues and returns a list with their title, status and number of affected users.
`search_errors`	Searches error events, such as exceptions and crashes with their stack trace, for counts, trends or single events.
`search_logs`	Searches application log entries, for counts, trends or single lines.
`search_traces`	Searches traces and spans, such as requests, API calls or database queries, for slowness and performance questions.
`search_metrics`	Searches metrics, such as counters, gauges and distributions, as rows or aggregates.
`search_profiles`	Searches performance profiles and the profiled transactions.
`search_replays`	Searches session replays, with rage clicks, dead clicks, visited pages and errors seen.
`find_dropped_events`	Shows the events dropped before being stored in Sentry, due to sampling, quota, filters or other reasons.
`get_sentry_resource`	Gets a Sentry resource by its link or ID, such as an issue, an event, a trace, a replay, a monitor or a dashboard.
`update_issue`	Changes an issue's status or assignee to resolve, reopen, assign, unassign or ignore it. Sentry marks it as destructive and it starts turned off.
`analyze_issue_with_seer`	Asks Seer, Sentry's analysis, for the root cause of an error, with its location in the code and concrete fixes.
`search_sentry_tools`	Searches the Sentry catalog for operations not shown up front, such as teams, releases or DSNs.
`execute_sentry_tool`	Runs a tool from the Sentry catalog found with search_sentry_tools. Sentry marks it as destructive and it starts turned off.

The limits

What the Sentry integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask you for confirmation in the chat before changing an issue if the admin turned that action on. execute_sentry_tool is a generic gateway: it runs any catalog tool the session has available, including some that create projects or teams. That is why both start turned off, and the admin decides in Connections whether to turn them on.
It does not fix the code. Seer proposes the cause and a fix; applying and publishing it is your team's work.
It does not see more than the account that authorized the connection. What that account cannot see in Sentry, the Met cannot see either.
It does not work with Sentry installed on your own servers: this connector points to the cloud service, mcp.sentry.dev.
It does not pay your Sentry plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Sentry

1

A Sentry account with access to the projects

The account your team uses to review the app's or site's errors. The Met works in the organizations and projects that account sees.
2

Connect it in Met

In Met, open Connections → Sentry → Connect. A Sentry window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about Sentry and Meteor

Yes. The Met opens the issue, the event or the trace from the Sentry link, without you having to copy the ID or the project name.

Because Sentry does not show them up front. They are in its catalog: the Met finds them with search_sentry_tools and runs them with execute_sentry_tool, which starts turned off until the admin turns it on.

Only if the admin turns on the action to change issues, which starts turned off. With it on, say in the Met's instructions whether it only assigns or can also resolve.

You do, with your Sentry account and plan. Meteor does not resell Sentry or charge for the actions your Met takes there.

Step by step