What's Atlassian OAuth 2.0 DCR redirect domain?

[Rafael Justo]

When adding an external MCP server, Atlasian will authenticate using the OAuth 2.0 DCR according to this documentation:

https://support.atlassian.com/organization-administration/docs/add-an-external-mcp-server-from-atlassian-administration/

What's the domain used in the redirect URL of the authentication flow? This is required so we can whitelist Atlassian when registering with our MCP server.

[Rafael Justo · Accepted solution]

For anyone looking for this, the domain appears to be:

id.atlassian.com

[Yashodip Jadhav]

Welcome to the Atlassian Community @Rafael Justo ,

From the documentation, Atlassian uses OAuth 2.0 Dynamic Client Registration (DCR) for external MCP servers, but I haven't found a published list of redirect domains that can be whitelisted in advance.

In cases like this, Atlassian typically provides the redirect URI during the OAuth registration/authorization flow rather than using a single documented domain. You may need an Atlassian team member to confirm the exact redirect URL or domain range required for your MCP server configuration.

Hopefully someone from the Atlassian team can clarify the supported redirect domains for external MCP integrations.

Hope this helps. If it resolves your issue, please consider accepting the answer so it can help others facing the same problem. Thanks!

[Rafael Justo]

Thank you, Tashodip! Unfortunately, we need some domain definition from Atlassian so our OAuth 2.0 DCR open registration is not so open 😄

[Tinker Fadoua]

Welcome to the Community @Rafael Justo !

Do you still need help? I only came across your question for the first time today.

Best,

Fadoua

[Rafael Justo]

Sorry, missed the notification regarding this message. Yeah, until I get this info, we won't be able to allow Atlassian to connect to our servers, since we try to control the open registration by limiting the possible redirect URL domains.