Atlassian authentication expired on the remote MCP server

Atlassian authentication expired on the remote MCP server

TL;DR: Re-authenticate: open /mcp, pick the atlassian server, choose Reconnect or Re-authenticate. Complete the Atlassian OAuth flow in the browser when prompted. Resume the operation; the refreshed grant applies immediately.

The error

Atlassian authentication expired.

Fix it

1. In your client, open the MCP panel (/mcp) and select the atlassian server.

Expected: The server shows an expired or disconnected state.

1. Choose Reconnect or Re-authenticate.

Expected: The browser opens the Atlassian OAuth consent screen.

1. Approve the requested scopes.

Expected: The flow completes and the client confirms connection.

1. Retry the Jira or Confluence tool call.

Expected: It succeeds.

When this applies

The remote Atlassian MCP server previously worked and now reports expired authentication on Jira or Confluence calls.

When this does NOT apply

PAT-based local servers do not use this flow; a 401 there means the token. First-time setup needs the initial OAuth grant, not a reconnect.

Tool compatibility

sooperset/mcp-atlassian remote server, OAuth

Also seen as

• Atlassian MCP re-authenticate
• Jira MCP OAuth expired
• Confluence MCP session expired

Why it happens

OAuth access tokens expire; the remote server relies on refresh or explicit re-auth. When the grant lapses, every tool call fails until the user completes the OAuth flow again.

Edge cases

• Some clients need a full restart after re-auth to drop the stale session.
• If re-auth loops, revoke the app grant in Atlassian account settings and start clean.
• Admin-approved apps may need an admin to re-consent.