Repository navigation
fix(mcp): Map common get_sentry_resource param aliases and URL shapes - #1829
Merged
Merged
Conversation
Accept issueUrl/resourceUrl as url and issueId/id as resourceId, infer the issue type for issue-shaped IDs, parse project event URLs, and point list or search URLs (issues, alerts, logs, traces, API) at the right tool instead of a generic unknown-URL error. Co-Authored-By: BYK <126780+BYK@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
BYK
approved these changes
Nov 3, 2026
BYK
enabled auto-merge (squash)
November 3, 2026 12:14
…source-param-aliases # Conflicts: # packages/mcp-core/src/toolDefinitions.json
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.
Two
get_sentry_resourceinput failures from the last 7 days insentry/mcp-server:urlorresourceTypemust be provided": ~4.6K/week. The calls carry the right value under the wrong key. The most common keys areresourceIdwithout a type (~830, all issue short IDs),issueId/issue_id(~900),resource+id(~630 / ~360, mostlyresource: "issue"),resourceUrl(~530) andissueUrl(~210)./projects/{project}/events/{eventId}/(~500), issue list URLs/issues/?query=…(~460), alert rule URLs (~380), Explore logs/traces search URLs (~250), and/api/0/…URLs (~180).What changed:
issueUrlandresourceUrlmap tourl, andissueIdandidmap toresourceId.issueIdalso impliesresourceType: issue. The schema grows from 683 to 710 tokens.resourceIdwith noresourceTyperesolves as an issue only when it looks like an issue ID: an uppercase short ID (PROJECT-123) or a numeric ID. Hex IDs, slugs and titles still need an explicit type./[organizations/{org}/]projects/{project}/events/{eventId}/. These resolve as an event by event ID, whichget_issue_detailsalready supports.search_issues,find_alert_rules/get_alert_rule,search_logs,search_traces, or the web URL for API links. Other unknown URLs keep the old error.Open question: multi-credential routing (
credential-routing.ts) reads the org only fromurl, so a call with only anissueUrl/resourceUrlalias falls back to the default credential. I left it alone because routing belongs to the #1669 work.via @BYK.
--
View Session [Sentry]