Repository navigation
feat(mcp): Add report_sentry_problem tool for agent feedback - #1517
Draft
sentry-junior[bot] wants to merge 2 commits into
Draft
sentry-junior[bot] wants to merge 2 commits into
sentry-junior[bot] wants to merge 2 commits into
Conversation
Let agents report problems with Sentry MCP tools, APIs, or docs. Reports are sent as User Feedback to the MCP server's own Sentry project, tagged with surface, target, and client family. Co-Authored-By: Armen Zambrano Gasparnian <armenzg@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
An empty --sentry-dsn still registers a Sentry client, so the tool reported success while nothing was sent.
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.
Agents that hit a broken MCP tool, an API that doesn't match its docs, or outdated docs have no way to tell us. This adds a minimal
report_sentry_problemtool that sends what they found as Sentry User Feedback to the MCP server's own project. This reuses the User Feedback flow we already have, likesentry cli feedback.A report includes the surface (
mcp,apiordocs), the target (tool name, endpoint or docs URL), what the agent expected, what actually happened, and an optional request, trace or event ID. Reports are tagged withagent_report.surface,agent_report.targetandagent_report.client_family, so they can be routed and grouped by surface and client. Because feedback is captured in the active request scope, it's linked to the MCP request trace.The tool is catalog-only: agents find it through
search_sentry_tools, so it doesn't count toward the direct tool limit. The tool description tells agents to report only problems with Sentry, to tell the user what will be sent first, and never to include secrets, prompt text or customer data. If Sentry telemetry isn't configured, the tool fails with a clear error and sends nothing.Open questions before this is ready:
tools/listsurface so agents see it without searching?agent_report.surface?via Armen.
--
View Junior Session [Sentry]