Rovo MCP server: how can a third-party MCP client join the Atlassian supported domains list?

Hi Atlassian team,

We build an MCP client (Blueticks Agents — WhatsApp AI agents for businesses) that connects customers’ Jira and Confluence through the Atlassian Rovo MCP server (OAuth 2.1 + PKCE). It works, but only after each customer’s org admin adds our domain under Atlassian Administration → Connectors → Atlassian MCP server → Add domain; otherwise users get “Your admin has blocked this domain”.

How can a third-party MCP client apply to be included in the Atlassian supported domains list, so customers can connect without the manual admin step?

Our domain / redirect URIs:

https://api.blueticks.co/agent-mcp/callback      (production)
https://stg-api.blueticks.co/agent-mcp/callback  (staging)

Use: a Jira/Confluence customer connects their own site so their agent can create issues and look up pages from WhatsApp conversations. All tools are off by default; the customer enables each one.

Thanks!

@noammazuz no published way to apply, as far as the docs go. The vendors are there though. The supported list already has smaller MCP clients like stilla.ai, runlayer.com and natoma.app next to Claude and ChatGPT, so Atlassian does add them.

Channel for app builders per their MCP server README is the Ecosystem Developer Portal. Raise it there with both callback URIs.

Until then, one entry. Brace patterns work, so https://{api,stg-api}.blueticks.co/** should cover both callbacks. Put that string in the admin onboarding notes. Custom lists cap at 20 (ROVO-1032).

API tokens skip the domain check, it’s OAuth 2.1 only. Doesn’t save the step though, an org admin has to switch token auth on first.