Matches a reported error to a known Sentry issue, reads how far it has spread, updates issue status and links, and traces it back to the release that shipped it.
205actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro updates a Sentry user's primary email address to keep your team contactable. Your support staff avoids missing alerts when email changes.
Ayro retrieves all email addresses for a Sentry user to verify contact info. Your team confirms the right notifications reach the right people.
Ayro pulls detailed information about a Sentry issue to diagnose crashes faster. Your team understands error context and impact immediately.
Each card is one request a support team gets, and the Sentry actions Ayro runs to close it.
Ayro searches the organisation's issues for what the customer described, opens the issue detail, and reads its tag values, so the reply can say whether this is known and how many people it is hitting.
Ayro updates the issue's status and assignment, applies the same change across the batch of duplicates behind it, and links the issue to the external ticket the customer is tracking.
Ayro fetches the alert rules on the organisation, creates one for a path that has newly turned noisy, and deletes the alert nobody reacts to any more, so on-call is paged for signal rather than habit.
Ayro lists the organisation's releases, retrieves the commits in the one deployed just before the errors started, and reads the deployment record, so the conversation narrows to a change rather than a theory.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Sentry actions it has and picks the ones a request needs.
Authorize the Sentry account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Sentry actions that close it and chains as many as the request needs.
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 freeSentry · Ayro
What can you do in Sentry without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Sentry.
Yes, as a read. List a Project's User Feedback returns the feedback attached to that project's events, so what one customer reported can be matched to the event an engineer is already looking at instead of staying stuck in a ticket.
All 205 actions your agent can call on Sentry, straight from the live MCP connection.
Retrieves detailed information for a Sentry project, given its existing organization and project ID or slug.
Add a custom symbol source to a Sentry project.
Invites a new member (or re-invites an existing non-accepted member) to a Sentry organization via email, allowing specification of organization and team roles.
Adds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user.
Adds an existing member of an organization to one of its teams; the member must already belong to the organization, and the team must also belong to that organization.
Grants a Sentry team access to a Sentry project within the specified Sentry organization.
Bulk mutate various attributes on issues within an organization.
Permanently removes issues from an organization.
Creates a workflow alert for a Sentry organization using the New Monitors and Alerts system.
Creates a Sentry dashboard with widgets for an organization; organization_id_or_slug and specified project IDs must be valid, and start/end datetimes (if absolute range) must form a logical ISO 8601 range.
Links a Sentry user to an external identity provider's user within a Sentry organization; the Sentry user must be an organization member, an active integration for the provider must be configured, and external_id is typically required for the external user.
Creates a Sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require Sentry integrations.
Creates a new monitor (type 'cron_job') within a Sentry organization to track scheduled tasks, allowing configuration of its name, slug (which must be unique if provided), status, owner, and muting preferences for incidents.
Creates a new team in a Sentry organization, requiring either a 'slug' or 'name' to define the team.
Creates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration.
Creates a Sentry project alert rule by defining conditions, actions, and optional filters using specific JSON structures (detailed in parameter descriptions) to automate responses to event patterns for an existing organization and project.
Registers a new webhook subscription for a Sentry project to send HTTP POST notifications to a specified URL for given events, provided the project has the 'servicehooks' feature enabled.
Creates a new deploy record in Sentry to track the introduction of a release version into a specific environment.
Creates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization.
Creates a new Sentry team (SCIM group) within an organization via the SCIM API.
Links an existing Sentry issue to an issue in an external service, or updates an existing link, requiring a configured Sentry App installation uuid.
Creates a new Sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules.
Creates a new Sentry organization member via a SCIM request for SAML integration; this action does not support setting secondary emails.
Deletes a custom integration (Sentry App) by its ID or slug.
⚠️ This endpoint is currently in beta and may be subject to change.
Bulk delete alerts for a given organization.
Permanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization.
Unlinks an external issue (e.g., from Jira/GitHub), identified by external_issue_id, from the Sentry app installation specified by uuid.
Unlinks a previously established external team from a Sentry team; this action does not delete either the Sentry team or the external team.
Deletes the link between an external user (from an integration provider like GitHub, Slack, GitLab, or MS Teams) and a Sentry user within the specified organization.
Same connection, same setup. Pick the next one your team already uses.
Apiflash is a website screenshot API for programmatically capturing web pages.
Explains why a job failed, triggers a pipeline rerun, manages contexts and environment variables, and reports flaky tests and credit spend.
Verifies credentials and presentations, resolves DID documents, reports what an account holds, and manages API keys, webhooks, and tags.
Checks domain availability and ownership, spins up free subdomains, manages VPS SSH keys, and reports on DNS, orders, and renewals.
Sends batches of templated email, explains bounces and complaints from real statistics, manages per-stream suppressions, and spam-scores a draft.
Creates uptime, page speed and heartbeat checks, reports alert and downtime history, maintains alert contact groups, and retunes or retires checks.

Authorize the account and your agent has all 205 actions from the first conversation.
