Authorization with the MCP server failed, keeps happening

[Jazor He]

When trying to connect to the Atlassian connector via Claude web app and desktop app, I got stuck in a loop of trying to connecting to the MCP server, navigating to my browser for to login and approval, the page is stuck at accepting the request for access to the Atlassian account (see image), and Claude app gives the following message:

Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: "ofid_d52bf9668307e143"

This was working before and I have used Claude to read and update Confluence and Jira but it has not been working intermittently since yesterday and has completely stopped working today.

 

[Dylan Wood]

That sounds incredibly frustrating. It’s possible that Claude has released a bug that prevents it from connecting to Atlassian’s OAuth2.1 system correctly. OAuth2.1 is the most secure and comprehensive OAuth specification, but it can also be quite temperamental. You’re not alone in this; many users are experiencing similar issues.

You’ll have a better chance of connecting using a personal access token (PAT) or a service account API Key. Instructions for obtaining a PAT are provided below. Unfortunately, Claude’s mobile, web, and desktop applications do not accept API Keys or PATs. I built a service called Bindify that acts as an intermediary that handles PAT/API Key authentication with Atlassian and provides you with a secure URL to insert into Claude’s custom connector setup.

If you’re interested in trying this approach, you can use the code **ATLASSIANCOMMUNITYAIAUTHFIX** for a month of free access (up to 5 Bindify connections, no credit card required). After that, it costs only $2 per month.

Here’s how to obtain an Atlassian PAT:

1. Go to Atlassian API Tokens.

2. Click on “Create new API Token with Scopes.”

3. Name the token and set its expiration (up to 1 year).

4. Click “Next.”

5. Select Jira.

6. Click “Next.”

7. Filter by Scope type: Classic.

8. Select all scopes on all pages.

9. Click “Next.”

10. Click “Create token.”

Disclaimer: I created Bindify after experiencing these authentication issues firsthand! I hope Claude will resolve this issue on their end. In the meantime, Bindify is here to help!

[Tomislav Tobijas]

Hi @Jazor He ,

I'd probably recommend reaching out to Atlassian Support with this (select Rovo when choosing a product/app). 👈

I'm not sure if there's a widespread problem with this or if it's isolated to your connection, but the team there should be able to troubleshoot this. 

Note that I did hear once or twice about similar issues and that it just resolved by itself, after a couple of hours, but still would recommend contacting support to check it out with them.

Cheers,
Tobi