Skip to content

feat(mcp-core): Add submit_feedback_to_sentry_team tool for agent friction reports - #1755

Merged
scttcper merged 4 commits into
mainfrom
feat/submit-feedback-tool
Oct 30, 2026
Merged

scttcper merged 4 commits into
mainfrom
feat/submit-feedback-tool

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Adds a submit_feedback_to_sentry_team tool 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:

  • Inputs: task, kind (missing / broken / confusing / idea), impact (blocked / worked_around / friction), description, and an optional toolName.
  • It calls captureFeedback() against the server's own Sentry client. Reports show up as User Feedback issues in our MCP project, tagged with feedback.kind, feedback.impact and feedback.tool. They also pick up the existing scope tags (transport, client and version) and the active trace. The tool returns the feedback event ID.
  • The message is run through scrubSensitiveText first, because feedback events skip beforeSend. It's then capped at Sentry's 4096-character feedback limit.
  • If Sentry has no DSN configured (for example, stdio without SENTRY_DSN), the tool can't deliver anything. In that case getAvailableTools hides it, so it never shows up in search or execute.
  • Reports go to the Sentry MCP maintainers, never into the user's Sentry org.

The tool is catalog-only, reachable through search_sentry_tools / execute_sentry_tool. I didn't add it to TOP_LEVEL_TOOL_NAMES because of the no-expand-top-level-tools rule.

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]

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>
@vercel

vercel Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
sentry-local Skipped Skipped Oct 30, 2026 5:38pm UTC

Request Review

@github-actions github-actions Bot added the risk: medium PR risk score: medium label Oct 30, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

❌ 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>
@sentry-junior sentry-junior Bot changed the title feat(mcp-core): Add submit_feedback tool for agent friction reports feat(mcp-core): Add submit_feedback_to_sentry_team tool for agent friction reports Oct 30, 2026
@scttcper
scttcper merged commit c25a3d1 into main Oct 30, 2026
36 of 37 checks passed
@scttcper
scttcper deleted the feat/submit-feedback-tool branch October 30, 2026 18:20

This branch was successfully deployed

1 active and 1 inactive deployments
Actions — 62b4d60b Deployed Oct 30, 2026 by sentry-junior[bot] via eval #1425
Preview — 62b4d60b Deployed Oct 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium PR risk score: medium

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant