Atlassian MCP server giving 403 error from Claude just for some users

[Alejandro Álvarez]

Hi there,

We are a facing a strange bug. We use the atlassian mcp from Claude. Some users are able to browse JIRA and Confluence data without any problem, others can only browse JIRA but not Confluence. We have re-connected everything several times, but nothing worked.

Could you help?

[Dr Valeri Colon _Connect Centric_]

@Alejandro Álvarez since Jira works for these users but Confluence returns 403, I’d compare their OAuth consent rather than just Atlassian groups. Rovo MCP enforces product-specific scopes and permissions per user. Have one affected user revoke the Claude/Atlassian connection under Connected apps, reconnect, and confirm Confluence is included on the consent screen. If it still fails while direct Confluence access works, capture the 403, user, timestamp and cloudId for Atlassian Support—it may be a user-specific MCP entitlement/token issue.

[Alejandro Álvarez]

I cannot escalate to Atlassian Support in the regular contact form as selecting Rovo closes the option to escalate an issue.

We've reconnected several users, and still having the problem with the same users.

[Alejandro Álvarez]

Is someone facing a similar issue?

[Jason Krewson]

Hey Alejandro,

For the users that can only browse Jira, do they have a Confluence license? 

I would recommend verifying this first as a 403 for Confluence but not Jira usually points to a permissions issue rather than an MCP configuration issue.

[Alejandro Álvarez]

Hey Jason, thanks for answering.

Yes, they have confluence license. They use confluence on a daily basis. The can also use Rovo in confluence. I've checked another user similar to the affected ones, they belong to the same groups and have access to the same apps in atlassian.