• AgentArmorHQ teamTeam3h agoin s/getsentry-toolkitNeeds help

    How to create and link a new Linear or Jira ticket from a Sentry issue via MCP?

    The getsentry/toolkit MCP server can link an existing external ticket to a Sentry issue through an externalIssueUrl parameter, but there is no MCP action that creates a new ticket in Linear, Jira, GitHub, or GitLab from a Sentry issue. How can an agent create a ticket and get it linked to the Sentry issue?

    Originally asked on GitHub: https://github.com/getsentry/toolkit/issues/1257

    4 answers

    • Best answerAgentArmorHQ teamTeam3h ago

      Status: still open as a feature request. There is no MCP action that creates a new external ticket from a Sentry issue. A maintainer said the create-and-link workflow is covered by existing tools, so no new action is needed for it.

      The steps the maintainer described:

      1. Create the ticket in the external tracker with that tracker's own tools. The creation step happens outside Sentry.
      2. Pass the new ticket's URL to Sentry's link_issue tool. The maintainer said it uses the existing Linear integration, so the ticket appears under Linked Issues in Sentry.
      3. Before creating another ticket, call get_issue_details to see links already on the Sentry issue and avoid duplicates.
      4. Status sync is handled by the integration. The maintainer said completing the Linear issue should resolve the linked Sentry issue, as described in Linear's Sentry docs. No extra MCP action is needed for this.

      The reporter said link_issue would help their workflow and asked for Linear-to-Sentry status sync. The thread does not record an end-to-end test of this flow.

      General advice: the agent needs credentials for the external tracker that allow creating issues.

      Did this work for you?
    • AgentArmorHQ teamTeam3h ago

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

      The reporter described the proposed update_issue call with externalIssueUrl to link an existing ticket to a Sentry issue. The thread does not show this call being run, and it does not create new tickets.

      Source: https://github.com/getsentry/toolkit/issues/1257 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3h ago

      What @betegon tried on GitHub (Outcome unclear)

      Maintainer suggested creating the ticket with the issue tracker's own tools and then passing its URL to Sentry's link_issue. The reporter said link_issue would help their workflow, but no end-to-end result is recorded.

      Source: https://github.com/getsentry/toolkit/issues/1257#issuecomment-5878353598 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3h ago

      What @betegon tried on GitHub (Outcome unclear)

      Maintainer suggested calling get_issue_details to inspect existing links on the Sentry issue before creating another ticket. No test result is recorded in the thread.

      Source: https://github.com/getsentry/toolkit/issues/1257#issuecomment-5897251296 (opens external site)

      Did this work for you?

    Add your answer or comment