AI agents need issue tools to expose richer integration metadata for linked external records, especially GitHub and Jira records such as linked PR/issue URLs, linked ticket keys, reasons, assignees, priority, and similar integration-specific fields.
Findings
get_issue_details already fetches /organizations/{org}/issues/{issueId}/external-issues/ and renders an ## External Issue Links section when records are returned.- The current external issue schema/output only includes
id, issueId, serviceType, displayName, and webUrl.
IssueSchema passes through upstream fields such as pluginIssues and pluginActions, and repo fixtures include those fields, but current issue formatting does not render them.- No current issue-related tool appears to expose read/write operations for integration-specific fields such as external assignee, reason, or priority.
Requested scope
Expose richer linked integration metadata through issue-related MCP tools so an AI agent can stay inside MCP context when cross-referencing a Sentry issue with linked GitHub/Jira records.
A follow-up implementation should decide whether this belongs in get_issue_details, a separate integration/external-issues tool, or both. Any write/update support for integration-specific fields will need upstream Sentry API behavior and scopes validated before implementation.
AI agents need issue tools to expose richer integration metadata for linked external records, especially GitHub and Jira records such as linked PR/issue URLs, linked ticket keys, reasons, assignees, priority, and similar integration-specific fields.
Findings
get_issue_detailsalready fetches/organizations/{org}/issues/{issueId}/external-issues/and renders an## External Issue Linkssection when records are returned.id,issueId,serviceType,displayName, andwebUrl.IssueSchemapasses through upstream fields such aspluginIssuesandpluginActions, and repo fixtures include those fields, but current issue formatting does not render them.Requested scope
Expose richer linked integration metadata through issue-related MCP tools so an AI agent can stay inside MCP context when cross-referencing a Sentry issue with linked GitHub/Jira records.
A follow-up implementation should decide whether this belongs in
get_issue_details, a separate integration/external-issues tool, or both. Any write/update support for integration-specific fields will need upstream Sentry API behavior and scopes validated before implementation.