You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search Jira MCP in the Add an integration search input
Click in Add Button of Jira MCP card
Click in View BUtton of JIra MCP card
Click in Add Connection
Click in Connect, this open a Jira login, the login is successfully.
Jira do a redirection to https://id.atlassian.com/error?error=unauthorized_client&error_description=Client%20is%20not%20allowed%20to%20use%20offline_access%20scope
Diagnostics / logs
No response
Before you submit
I searched the open issues for a duplicate.
I removed all keys, tokens, and credentials from this report.
hey @jrecinos-applaudo i just added a jira integration following the step u described, im not able to reproduce this issue on my end.
but when i added a jira connection with the mcp url you provided (https://mcp.atlassian.com/v1/mcp/authv2), the same error came up for oauth. removing the authv2 at the end works fine (i.e. https://mcp.atlassian.com/v1/mcp/), could u try this and see if it works for u?
edit:
actually i think an fix is needed.
executor's OAuth client metadata only advertizes authorization_code, but atlassian's /authv2 flow requested offline_access (permission to obtain refresh tokens).
and atlassian rejected this mismatch and showed Client is not allowed to use offline_access scope.
Activity
[-][bug] Can`t add Jira MCP[/-][+][bug] Can't connect to Jira MCP[/+]baggiiiie commentedon Sep 10, 2026
hey @jrecinos-applaudo i just added a jira integration following the step u described, im not able to reproduce this issue on my end.
but when i added a jira connection with the mcp url you provided (https://mcp.atlassian.com/v1/mcp/authv2), the same error came up for oauth. removing the
authv2at the end works fine (i.e.https://mcp.atlassian.com/v1/mcp/), could u try this and see if it works for u?edit:
actually i think an fix is needed.
executor's OAuth client metadata only advertizes
authorization_code, but atlassian's/authv2flow requestedoffline_access(permission to obtain refresh tokens).and atlassian rejected this mismatch and showed
Client is not allowed to use offline_access scope.