The MCP Auth expires too fast

[Fabian E.]

I'm using the Atlassian MCP in Claude Code, which is very helpful. Unfortunately, after a few minutes in Claude Code, it gets a 401 error, since seemingly the MCP OAuth token expires already after a few minutes. Claude Code cannot renew the token by itself, so i have to do that manually, and then continue work in Claude Code, which is pretty annoying. How can i get a token that is valid for at least multiple hours, or even weeks?

[Jochem Berends]

Atlassian MCP is unusable due to the longevity of their auth tokens. Needing to reauthenticate twice a working day is horrible. Why can;t I inject my personal access token into it; that is longlived and properly in control. This is worthless. 

Is there any open source MCP for atlassian that has proper access to the API of jira (or confluence) that can use Personal Access API Tokens?

[Dr Valeri Colon _Connect Centric_]

@Fabian E. @Liam Hall @Pavel Shmelev You can’t. The Atlassian MCP server only issues short-lived OAuth tokens in the current preview, and external clients like Claude Code can’t refresh them automatically. After a few minutes the token expires, leading to 401s. Atlassian hasn’t released long-lived or refreshable tokens yet, so manual reauth is the only option until the MCP auth flow is expanded.

[Liam Hall]

Here for this too

[Pavel Shmelev]

I have a similar issue: when I'm trying to run two instances of Claude Code that rely on the same Atlassian user OAuth token on different machines it seems they expire instantly after the other MCP gets authenticated.

It would be nice to keep several sessions live so I can perform parallel workflow with JIRA on behalf of the same user but with different instances of Claude Code

[Mayhew Park]

This!