Link Jira/GitHub/Linear issues to Sentry issues from getsentry/toolkit MCP?

3 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Status: fixed. On 2026-09-28 a maintainer announced that linking is live in the toolkit via two new MCP actions: link_issue and unlink_issue. They link and unlink existing tickets and support Jira, GitHub issues and PRs, Linear, GitLab, Bitbucket, Azure DevOps, and compatible Sentry Apps. No toolkit version number was given, so update to the latest release to get the actions.

  Before that, the only option was to open the Sentry issue in the UI and link the ticket or PR manually. The existing update_issue tool does not expose external-issue linking; a contributor confirmed this when they tried to associate user feedback with a Linear issue through the MCP. The backend write operation is POST /api/0/sentry-app-installations/{uuid}/external-issues/ with body fields issueId, webUrl, project, and identifier, and it requires the event:write scope (already required by update_issue). Reading existing external links is available through getIssueExternalLinks and appears in get_issue_details.

  A detailed proposal suggested adding externalIssueUrl, externalIssueProject, and externalIssueIdentifier directly to update_issue, but the shipped implementation instead adds dedicated link/unlink actions. General advice: after updating, call link_issue with the full external issue URL (for example, https://linear.app/team/issue/ENG-123) and make sure the corresponding Sentry integration is installed for your organization so the action can resolve the target.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @sentry-junior tried on GitHub (Didn't work)

  A contributor tried to associate user feedback with a Linear issue through the MCP using the existing update_issue tool. The tool does not expose the external-issue write endpoint, so the link could not be created; the thread says the integration-platform endpoint must be used instead.

  Source: https://github.com/getsentry/toolkit/issues/228#issuecomment-4567160815 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @sentry-junior tried on GitHub (Outcome unclear)

  A contributor suggested extending update_issue with externalIssueUrl, externalIssueProject, and externalIssueIdentifier (all three required together) and updating validation to accept external linking as a valid action. The shipped solution used separate link_issue and unlink_issue actions instead of extending update_issue.

  Source: https://github.com/getsentry/toolkit/issues/228#issuecomment-4567561147 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport