Sentry MCP `update_issue` ignores forever despite "until it escalates" reply
I'm using the hosted Sentry MCP server (latest) with Claude 2.1.87 on macOS 26.3.1. When I call
update_issuewithstatus: 'ignored', the tool replies "The issue is now ignored and will not generate alerts until it escalates", but the Sentry UI shows the issue is ignored permanently. Is ignore-until-escalating supported at all?Originally asked on GitHub: https://github.com/getsentry/toolkit/issues/873
4 answers
Status: explained — the maintainers confirmed
update_issuecurrently supports only the permanent ignore; no fix is mentioned in this thread, but a contributor planned to add granular ignore support via a PR.The hosted Sentry MCP
update_issuetool acceptsstatus: 'ignored', but the ignore is always permanent. A maintainer said the tool is "super bare bones" and the only ignore status supported is perma ignore, so the reporter's observed behavior (UI shows ignore forever, despite the tool reply mentioning escalation) is expected. Only usestatus: 'ignored'when you intend a permanent ignore.One contributor asked whether a PR rewording the tool response to explicitly say "permanently ignored" would be welcome; the maintainer said they would rather get the whole ignore granularity supported but are open to a PR. Another contributor said they planned to open a PR within about a week to add granular ignore support (ignore until escalating, etc.), after mapping the Sentry API with Claude and captured HTTP requests. The maintainer noted the repo uses a mocks package with Sentry pseudo-fixtures for tool tests and that tests passing is the main bar for review, though no PR is referenced in this thread.
General advice: until granular support lands, implement ignore-until-escalating decisions in your Claude skill/prompt logic (for example, only call
update_issueto ignore when your own conditions for it are met), since the MCP tool cannot express that state.Did this work for you?What @colbymelvin tried on GitHub (Didn't work)
Called
update_issuewithstatus: 'ignored'expecting ignore-until-escalating based on the tool's response; the Sentry UI instead showed the issue was permanently ignored.Source: https://github.com/getsentry/toolkit/issues/873 (opens external site)
Did this work for you?What @colbymelvin tried on GitHub (Outcome unclear)
Asked whether a PR changing the tool response to say "permanently ignored" would be accepted; the maintainer replied they would rather support the full feature but are open to a PR.
Source: https://github.com/getsentry/toolkit/issues/873#issuecomment-4156238186 (opens external site)
Did this work for you?What @colbymelvin tried on GitHub (Outcome unclear)
Planned to open a PR within about a week to add granular ignore support to
update_issue, after enumerating the Sentry API with Claude and captured HTTP requests.Source: https://github.com/getsentry/toolkit/issues/873#issuecomment-4162814633 (opens external site)
Did this work for you?
Related questions
- Does getsentry/toolkit support granular token scopes (read-only default + 401 upgrade)?
- How to query Sentry issues without OpenAI API calls in the official Sentry MCP server?
- Sentry MCP search_issues/search_events fail: 'Incorrect API key provided' on mcp.sentry.dev
- Sentry MCP search_issues fails with "OPENAI_API_KEY required" when EMBEDDED_AGENT_PROVIDER is anthropic
- How do I get breadcrumbs in Sentry issue details with sentry-mcp?