fix(sentry): Filter UserInputError from Sentry

[sentry]

This PR addresses an issue where expected UserInputError and ConfigurationError exceptions, particularly those originating from parseIssueId due to invalid input, were being captured and sent to Sentry as issues.

These errors represent user-facing validation failures rather than actual bugs in the application, leading to noise in Sentry.

The fix modifies the sentryBeforeSend function in packages/mcp-core/src/telem/sentry.ts to check for UserInputError and ConfigurationError types. If an event's primary exception is one of these types, sentryBeforeSend now returns null, preventing the event from being sent to Sentry.

Fixes MCP-SERVER-G40

_{Comment @sentry <feedback> on this PR to have Autofix iterate on the changes.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b1138dc. Configure here.}

[cursor]

Config errors silently dropped from Sentry

High Severity

Filtering all ConfigurationError events in sentryBeforeSend also drops the intentional logIssue calls from formatServerConfigError on HTTP transport. Those alerts notify operators about server-side config failures, and the generic user message claims the operator was notified.

 

^{Reviewed by Cursor Bugbot for commit b1138dc. Configure here.}