Your agent can now manage Alerts and Metric Monitors, link external tickets to Sentry issues, and see suspect commits while investigating issues.

These updates shipped to the hosted Sentry MCP server at mcp.sentry.dev between September 15 and September 30, 2026.

Manage Alerts and Metric Monitors

• Alerts: Create, update, and delete alert rules, including their conditions, notification actions, and connections to issue streams or monitors. Your agent can inspect existing rules and their project scope, and use get_alert_options to discover available actions, integrations, and monitor sources.
• Metric Monitors: Create, update, and delete metric monitors, and inspect their queries and Static, Percent, or Dynamic detection settings.

Reads are part of the default Inspect Issues & Events skill. Writes require the Manage Projects & Teams skill.

Already connected? If you connected before this update, re-authorize to grant the new alerts:write OAuth scope and enable these write operations.

By Miguel Betegón in #1330, #1331, #1313, #1333, #1334, #1335, and #1336.

Link external issues

link_issue attaches an existing Jira, GitHub, GitLab, Bitbucket, Azure DevOps, or Sentry App ticket, or a GitHub pull request, to a Sentry issue by URL. unlink_issue removes the reference without deleting the ticket. Both require the Triage Issues skill. By David Cramer with Miguel Betegón in #1027.

Other improvements

• get_issue_details now includes the suspect commit's SHA, message, author, and source. By Hasnain with Miguel Betegón in #1339.
• find_organizations, find_projects, and find_teams page through results with nextCursor instead of stopping at 25. By Max Beech with Miguel Betegón in #1319 and #1352.

Fixes

• search_events fails less often to generate a query: models no longer invent invalid environment values, and a valid query found on the final attempt is no longer discarded. By Jamie in #1346 (with Miguel Betegón) and #1349.
• get_issue_details and get_sentry_resource no longer return 404s for projects with legacy mixed-case slugs. With David Cramer in #1328.
• Codex connections no longer fail when its client metadata can't be fetched. By Miguel Betegón in #1312.
• get_alert_options works for organizations with Sentry Apps installed. By Miguel Betegón in #1338.
• update_issue no longer fails when a reason contains null characters (#1326).
• mcp.sentry.dev no longer crashes in browsers without WebAssembly (#1345).

Are you using the stdio MCP server?

If you're using our npm package @sentry/mcp-server, versions 0.40.0 through 0.42.0 include the Alert and Metric Monitor tools and fixes for single-tenant *.my.sentry.io hosts (#1332, #1341 by Miguel Betegón).

Since 0.41.0, self-hosted connections leave Seer off by default; add seer to --skills or pass --all-skills to enable it. By Denis Chistyakov in #1321.

These npm versions do not include issue linking, suspect commits, pagination, or the search_events fixes.