Rovo MCP Server: Repeated Re-Authentication is Breaking Developer Workflows — Needs Priorit

[Devesh Mittal]

  Body:                                                                         

  Hi Rovo MCP Team (@Josh Frank @Dilip Venkatesh @Erick Kahinga),               

  We're experiencing constant re-authentication prompts with the Rovo MCP Server

   that are severely impacting our developer workflow at FLOW Living

  (flowlife.atlassian.net).                                                     

  The problem:                                 

  - OAuth sessions expire unpredictably and far too quickly

  - No documentation exists on session duration or expiration policies          

  - Developers are forced to re-authenticate multiple times per day, breaking

  flow                                                                          

  What we're asking for:                       

  - Priority fix for OAuth session persistence — sessions should last           

  hours/days, not minutes                                                       

  - Clear documentation on session lifetime and token expiration policies

  - Confirmation that API token auth (announced Feb 24) provides stable,        

  long-lived sessions as a workaround                                

  This is a known issue reported across multiple threads:

  - https://community.atlassian.com/forums/Jira-questions/Unstable-Atlassian-MCP

  -Server-Connection/qaq-p/3180324                                              

  - https://community.atlassian.com/forums/Rovo-questions/Atlassian-MCP-stopped-

  working-failing-during-OAuth-flow/qaq-p/3119595                               

  - https://community.atlassian.com/forums/Rovo-questions/Trouble-authenticating

  -to-Atlassian-Rovo-Remote-MCP-Server-mcp/qaq-p/3167086                        

  Would appreciate a response from the team on timeline and workarounds.

  Thanks,                                                            

  Devesh Mittal — FLOW Living                                                   

[Dilip Venkatesh]

@Devesh Mittal - 

Thanks for the detailed report — we understand how disruptive re-authentication prompts can be to developer flow, and we take this seriously.

To help us investigate and prioritize effectively, could you share a few more details?

•  Which MCP client are you using? (e.g., Claude Desktop, Cursor, VS Code Copilot, Windsurf, custom integration, etc.) — and which version, if known.
• How frequently are you seeing re-auth prompts? For example, is it every ~15 minutes, every hour, once per session restart, etc.? Is it consistent across your team or does it vary by developer?
•  Do you have any rough stats or patterns? For instance:
  •  Does it happen after a period of inactivity, or mid-use?
  • Is it tied to specific tools/actions, or does it seem random?
  • Approximately how many developers on your team are affected?
  • Did this start recently or has it been ongoing since you first set up?

This information will help us narrow down whether this is related to token refresh behavior, client-side session handling, or something else entirely.

Additionally we also support API tokens as an auth method which would alleviate some of these re-auth concerns. 

Thanks,

Dilip