Repository navigation
feat(mcp-core): Add submit_feedback_to_sentry_team tool for agent friction reports - #1755
Merged
Merged
Conversation
Agents can report missing, broken, or confusing tools. Reports are sent as Sentry User Feedback to the MCP server's own Sentry project. Co-Authored-By: Scott Cooper <scott.cooper@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Contributor
There was a problem hiding this comment.
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 93915c3. Configure here.
Without a DSN the tool cannot deliver feedback, so drop it from the available tools instead of returning submitted: false. Co-Authored-By: David Cramer <david@sentry.io> Co-Authored-By: Scott Cooper <scott.cooper@sentry.io>
Co-Authored-By: Scott Cooper <scott.cooper@sentry.io> Co-Authored-By: David Cramer <david@sentry.io>
Makes the destination explicit so agents don't confuse it with the user's own Sentry org. Co-Authored-By: Scott Cooper <scott.cooper@sentry.io> Co-Authored-By: David Cramer <david@sentry.io>
scttcper
approved these changes
Oct 30, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Adds a
submit_feedback_to_sentry_teamtool so agents can tell us when they hit friction with Sentry MCP. That covers a missing capability, a broken tool, or a confusing tool or description. It's modeled on Clerk's agent feedback tool. The name says where the feedback goes, so agents don't confuse it with the user's own Sentry org.The tool is deliberately simple:
task,kind(missing/broken/confusing/idea),impact(blocked/worked_around/friction),description, and an optionaltoolName.captureFeedback()against the server's own Sentry client. Reports show up as User Feedback issues in our MCP project, tagged withfeedback.kind,feedback.impactandfeedback.tool. They also pick up the existing scope tags (transport, client and version) and the active trace. The tool returns the feedback event ID.scrubSensitiveTextfirst, because feedback events skipbeforeSend. It's then capped at Sentry's 4096-character feedback limit.SENTRY_DSN), the tool can't deliver anything. In that casegetAvailableToolshides it, so it never shows up in search or execute.The tool is catalog-only, reachable through
search_sentry_tools/execute_sentry_tool. I didn't add it toTOP_LEVEL_TOOL_NAMESbecause of theno-expand-top-level-toolsrule.Follow-up: agents that are stuck may not go looking for this tool. The next step is to point to it from responses that likely mean a bug, such as unexpected errors, 5xx errors, embedded-agent failures, and empty results from natural-language search.
--
View Session [Sentry]