My company has strict data sovereignty requirements and all data must be stored and processed within Australia.
From what I can see in online documentation, the new(ish) Rovo MCP Server is not pinned to the same region as Jira/Confluence/etc. Is anyone able to confirm that the Rovo MCP Server does not support region restriction?
@John Ginn welcome to the community. Short answer: you can’t currently enforce full regional processing for Rovo/MCP.
Data residency (stored data) → can be pinned for Jira/Confluence
Rovo/MCP processing → not region-pinned
LLM processing → may occur outside your region (e.g., US-based providers)
Also, MCP isn’t just a “stateless gateway”—it can handle transient processing, which still falls outside residency guarantees. So if you need strict AU-only processing (including inference), Rovo likely won’t meet that requirement today.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can only pin Data Residency. Rovo MCP doesn't really save data. It's just a gateway to Atlassian's API. The Apps accessed still reside whereever you pinned them.
Rovo itself can be pinned to a region, but the LLMs used are mostly hosted in the US (OpenAi etc.).
So: Data in Transit/Data processing is not pinned to your Region anyway, only Data Residency.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on the current Atlassian Rovo MCP Server documentation, I don’t see region pinning or customer-selectable data residency controls documented for the MCP server in the same way customers expect for Jira or Confluence data residency.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.