Junior can't submit tickets to Sentry's internal Jira Service Management desks (IT, HR/People Ops, Legal, Procurement). The Atlassian Remote MCP Server is now GA and follows the same provider plugin pattern already used for Linear and Notion, making it the lowest-friction path to add this capability.
Current behavior
There is no way to file an IT, HR, Legal, or Procurement ticket through Junior. Users must navigate to getsentry.atlassian.net portals directly.
Gap
Internal service requests (laptop issues, access requests, legal reviews, procurement approvals) are a common interruption from the keyboard. Junior already has the integration surface for task creation in Linear; extending it to JSM desks removes a meaningful context switch for employees.
Proposed approach
Add the Atlassian Remote MCP as a provider plugin (same pattern as Linear/Notion) and write a jira skill that routes requests to the correct JSM project.
- Provider:
https://mcp.atlassian.com/v1/mcp/authv2, OAuth 2.1 or API token
- Auth model: either per-user OAuth (tickets filed as the requestor) or a shared service account token — tradeoff is attribution vs. operational simplicity
- Skill logic: maps desk intent → project key + issue type →
jira_create_issue tool call; returns issue URL
- Confirmed Sentry JSM desks: IT (live), Legal (live), HR/People Ops (portal 8), Procurement; project keys need lookup from
getsentry.atlassian.net
Known gaps in official MCP
The official Atlassian MCP exposes Jira Software-style workitem creation, not JSM customer portal semantics (servicedeskapi/request with requestTypeId). For internal employee requests this is acceptable — creating into the JSM project directly works fine. If portal-native request type routing becomes important, the community sooperset/mcp-atlassian server (72 tools, includes jira_service_desk toolset) is a fallback, at the cost of self-hosting.
Open question before building
Does IT prefer tickets attributed to the individual requestor (requires per-user OAuth) or is a bot account sufficient?
Junior can't submit tickets to Sentry's internal Jira Service Management desks (IT, HR/People Ops, Legal, Procurement). The Atlassian Remote MCP Server is now GA and follows the same provider plugin pattern already used for Linear and Notion, making it the lowest-friction path to add this capability.
Current behavior
There is no way to file an IT, HR, Legal, or Procurement ticket through Junior. Users must navigate to
getsentry.atlassian.netportals directly.Gap
Internal service requests (laptop issues, access requests, legal reviews, procurement approvals) are a common interruption from the keyboard. Junior already has the integration surface for task creation in Linear; extending it to JSM desks removes a meaningful context switch for employees.
Proposed approach
Add the Atlassian Remote MCP as a provider plugin (same pattern as Linear/Notion) and write a
jiraskill that routes requests to the correct JSM project.https://mcp.atlassian.com/v1/mcp/authv2, OAuth 2.1 or API tokenjira_create_issuetool call; returns issue URLgetsentry.atlassian.netKnown gaps in official MCP
The official Atlassian MCP exposes Jira Software-style workitem creation, not JSM customer portal semantics (
servicedeskapi/requestwithrequestTypeId). For internal employee requests this is acceptable — creating into the JSM project directly works fine. If portal-native request type routing becomes important, the communitysooperset/mcp-atlassianserver (72 tools, includesjira_service_desktoolset) is a fallback, at the cost of self-hosting.Open question before building
Does IT prefer tickets attributed to the individual requestor (requires per-user OAuth) or is a bot account sufficient?