nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Hi, how can I connect Cursor with Jira?

Mahanth Prudhvi P

I have already connected Claude with Jira, and the setup was quite straightforward using the Atlassian connector in Claude, which uses MCP.

My expectation for the Cursor–Jira integration is the following: Cursor would have access to the current codebase, and through the Jira integration, it could fetch the details of a specific Jira ticket describing the required changes. Cursor would then use the ticket details along with the existing code to understand the requirement and suggest the necessary code changes.

The Jira access would ideally be read-only—Cursor should be able to fetch ticket details but not modify Jira tickets.

Please correct me if I have misunderstood how the Cursor–Jira integration works or if there is a better approach to achieve this.

Thank you

Mahanth

Accepted answers

Josh

Hi Mahanth, what you describe (Cursor reads the ticket and uses it with the codebase) is the same MCP pattern you used with Claude, and it works well:

In Cursor, open Settings → MCP (Tools & Integrations). Either add Atlassian's plugin, or add a custom server with the URL https://mcp.atlassian.com/v2/mcp (the older /v1/sse endpoint is no longer supported).
Cursor opens a browser window for Atlassian OAuth. Sign in and pick your site.
In chat, something like: "Read PROJ-123 from Jira, then propose the code changes in this repo that satisfy its acceptance criteria."

Read-only: the MCP server acts with your own Jira permissions, so it can never do more than you can. To stop it writing at all, go to Cursor's MCP settings, expand the Atlassian server and switch off the create/edit/transition/comment tools, leaving only the read/search ones. Your org admin can also limit the Rovo MCP server to read access in Atlassian Administration, if you want that enforced centrally rather than per laptop.

The permission list Nikola posted belongs to a different feature: Cursor's own Jira integration for Cloud Agents. That one is triggered by assigning a work item or @mentioning Cursor, and it writes status and PR links back to Jira. For "read the ticket while I code locally," MCP is the better fit.

All comments

Nikola Perisic

Hello @Mahanth Prudhvi P

These are the permission has for Jira:

User Identification: Identifies the specific Jira user starting or managing a Cloud Agent.
Read Access: Reads work item fields, titles, descriptions, comments, and related project context.
Write & Update Access: Posts status updates, completion summaries, and automatic pull request links back to the work items.
Event Subscriptions: Receives webhooks/events when work items are assigned directly to Cursor or when @cursor is mentioned in a comment

Josh

Hi Mahanth, what you describe (Cursor reads the ticket and uses it with the codebase) is the same MCP pattern you used with Claude, and it works well:

In Cursor, open Settings → MCP (Tools & Integrations). Either add Atlassian's plugin, or add a custom server with the URL https://mcp.atlassian.com/v2/mcp (the older /v1/sse endpoint is no longer supported).
Cursor opens a browser window for Atlassian OAuth. Sign in and pick your site.
In chat, something like: "Read PROJ-123 from Jira, then propose the code changes in this repo that satisfy its acceptance criteria."

Mahanth Prudhvi P

Thank you @Josh for the clarification. Appreciate the detailed steps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

jira-cloud

cursor