Trying to establish my Atlassian Cloud account. Totally confused about how to set that up.

Question

Hi,

I'd like to check on the integration status of my Northbay Restaurant Design account, and also

I own the existing Loom workspace “Northbay Restaurant Design.” My Loom personal settings confirm that my account is connected to Atlassian.

When connecting Perplexity through Atlassian Rovo MCP, authorization stops with: “Your account isn’t associated with a supported site. Rovo MCP connects with Atlassian sites that use apps like Jira or Confluence.”

Opening admin.atlassian.com takes me to “Create organization,” not an existing organization.

How can I enable MCP access to my existing Loom workspace and videos? Please confirm whether workspace migration or site linkage is required, whether it requires another subscription, and how to preserve existing videos, folders, permissions, and URLs. I do not want to create a duplicate workspace.

Thank you.

Stanley “Stan” Gardiner · Answer

Good morning, and thank you for the comment back here. I'm curious: how do we move from the old Loom workspace into the Atlassian cloud? We have not seen an invite yet or any communication to that effect.

Ciro · Answer

Hello,

That error is about where your Loom workspace lives, not about Perplexity: *.perplexity.ai is already on Atlassian's supported MCP domain list.

* Rovo MCP only reaches Loom when the Loom workspace is linked to an Atlassian Cloud site, and the Loom tools are only on the v2 endpoint (https://mcp.atlassian.com/v2/mcp). Worth checking Perplexity points there.
* admin.atlassian.com sending you to "Create organization" usually means your account isn't an admin of any Atlassian organization yet, so the workspace hasn't been integrated. Atlassian has been moving existing Loom workspaces into their own organization automatically, on a rolling basis since August 2025, and you get an email and a banner in the workspace when it's done. The docs have no self-serve step for this, so if you haven't seen that notice, Loom support can tell you when yours is due.
* Don't create a new Loom from Atlassian Administration in the meantime. That makes a new workspace instead of linking yours.
* On your data, the integration FAQ says you don't lose any video content, and existing permissions and workspace settings stay the same. It doesn't mention URLs or folders, so ask about those in the same ticket.

One thing I couldn't confirm: the error mentions sites with Jira or Confluence, and I couldn't find whether a Loom-only organization is enough for MCP. Worth asking that too.