Atlassian MCP createJiraIssue fails: missing *:jira:agent-interface scopes (edit/read work)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Official Atlassian MCP plugin in Cursor can read and edit Jira issues, but createJiraIssue always fails with missing OAuth scopes.

Exact error:
Insufficient scopes for “createJiraIssue”. Required: [read:jira:agent-interface, write:jira:agent-interface, search:jira:agent-interface].

Works: getAccessibleAtlassianResources (site shows read-write), getJiraIssue, editJiraIssue, mcp_auth.
Fails: createJiraIssue only.

Org admin: Atlassian Administration → Rovo → Rovo MCP server → Permissions → Jira Write is Allowed.
Site: crona.atlassian.net

Steps to Reproduce

  1. Install/enable official Atlassian plugin (Customize → MCPs; no URL field).
  2. Authenticate via mcp_auth / Connect.
  3. Confirm getJiraIssue and editJiraIssue work.
  4. Call createJiraIssue for any project (e.g. CLABS Task).
  5. Observe Insufficient scopes for createJiraIssue requiring *:jira:agent-interface.

Also tried: revoke all Cursor OAuth grants at id.atlassian.com (had 8), re-enable MCP, reconnect, probe create again — same error.

Expected Behavior

After org Write is Allowed and user consents to Write, createJiraIssue should succeed the same way editJiraIssue does.

Operating System

Windows 10/11

Version Information

Version: 3.21.18
OS: Windows 10/11
Plugin: Official Atlassian (plugin-atlassian-atlassian)
MCP: Customize → MCPs → Atlassian (marketplace plugin; no URL shown)

For AI issues: which model did you use?

Agent / Composer (Auto)

Additional Information

Workaround: create issues in Jira web UI; then edit/transition via MCP.

This looks like the Cursor Atlassian plugin OAuth token is missing agent-interface write scopes used by create, while edit uses a different path.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @CS35, thanks for the report and for already trying the revoke and reconnect steps.

The Atlassian plugin now connects to Atlassian’s newer MCP endpoint, where creating issues needs the newer “agent-interface” Jira scopes. Atlassian’s own docs say:

Any incompatible clients will need to clear cached clientIds or .well-known credentials to support continued use of Atlassian MCP.

Try this:

  1. Open Customize → MCPs
  2. Click Logout (or Disconnect) on the Atlassian entry.
  3. Fully quit and restart Cursor.
  4. Go back to the Atlassian entry and click Connect.
  5. Finish the connection flow
  6. In a new Agent chat, ask it to call getAccessibleAtlassianResources and then createJiraIssue in your CLABS project.

Does creating new jira issues still fail after step 6? Either way, could you paste the exact scopes list getAccessibleAtlassianResources returns for crona.atlassian.net? That tells us whether the write scope is actually on the token.strong text

7

@Colin Thanks — followed your steps carefully, twice.

Each time:

1. Customize → MCPs → Disconnect / Logout on Atlassian

2. Also disabled / toggled off the Atlassian MCP entry

3. Fully quit Cursor (not just close the window)

4. Restarted Cursor

5. Re-enabled / Connect on Atlassian and finished the OAuth consent flow

6. New Agent chat: getAccessibleAtlassianResources, then createJiraIssue on CLABS

**Result:** create still fails with the same error:

```

Insufficient scopes for “createJiraIssue”. Required: [read:jira:agent-interface, write:jira:agent-interface, search:jira:agent-interface].

```

Read / edit still work (e.g. getJiraIssue on CLBA-66).

**Exact getAccessibleAtlassianResources response** (this is all it returns — no granular agent-interface scope list):

```json

{

“resources”: [

{

  "cloudId": "abcf66b1-0edb-45eb-aa80-acae5c30334e",

  "url": "crona\[.\]atlassian\[.\]net",

  "products": \[

    { "id": "jira", "access": "read-write" }

  \]

}

]

}

```

Plugin .mcp.json points at mcp[.]atlassian[.]com/v2/mcp

One reconnect attempt briefly attached the wrong site (crona-team[.]atlassian[.]net only). After another disconnect/reconnect we are back on crona[.]atlassian[.]net, but create still fails.

Happy to try any further cache-clear steps you suggest.

15

Hey @CS35, thanks for running through that twice.

Let’s try one broader reset on the Cursor side and one check on the Atlassian side:

  1. Press Ctrl+Shift+P and run Cursor: Clear All MCP Tokens. This signs you out of every MCP server, so you’ll need to reconnect any others you use too.
  2. Fully quit Cursor and reopen it.
  3. Open Customize → MCPs and click Connect on Atlassian, then finish the consent flow.
  4. In a new Agent chat, ask it to run searchJiraIssuesUsingJql on crona.atlassian.net with the JQL project = CLABS ORDER BY created DESC, then try createJiraIssue again.
  5. Ask your Atlassian org admin to check Atlassian Administration → Rovo → Rovo MCP server → Permissions and confirm that Jira Search (not just Write) is set to Allowed.

The create tool needs the Jira Read, Write and Search permissions together, and your read and edit calls working suggests Read and Write are already fine.

If search also fails with “Insufficient scopes”, allowing Jira Search in that admin page and reconnecting should fix create. If search works and create still fails after a clean reset, Cursor is requesting the permissions Atlassian advertises, so the next step would liekly be Atlassian support.

16

@Colin That fixed it — thanks!

What we did:

  1. Allowed Jira Search (in addition to Read/Write) under Atlassian Administration → Rovo → Rovo MCP server → Permissions
  2. Cursor: Clear All MCP Tokens
  3. Reconnected / re-authenticated the Atlassian MCP

Then in a fresh Agent chat:

  • getAccessibleAtlassianResources → crona.atlassian.net with jira access read-write (still no granular agent-interface scope list in that response)
  • searchJiraIssuesUsingJql on project = CLABS → succeeded
  • createJiraIssue on CLABS → succeeded (created throwaway CLABS-55)

So the missing piece was Search on the Atlassian org side, plus a clean MCP token reset. Appreciate the clear steps.