OAuth Domain Whitelisting Limitations with Atlassian Remote MCP Server Integration

Zeeshan Parwez

Hello Atlassian Developer Community,

I'm working on integrating the Atlassian remote MCP server with a custom application hosted on our domain, but I've encountered a significant roadblock with the OAuth authorization flow .

Problem Description

When attempting to complete the OAuth flow by redirecting users to the authorization endpoint, I consistently encounter this error message:

"The redirect URI is not allowed, the URL is not part of Atlassian whitelisted domains for registered MCP Clients. Redirect URI <our_domain_uri>"

Current Situation

Based on my research through community discussions and documentation, it seems the Atlassian remote MCP server maintains a restrictive domain whitelist that appears to support:

• Specific IDE integrations

• Claude-related tools

• localhost URIs for development purposes

This explains why the integration functions correctly in my local development environment but fails when deployed to our production domain .

Key Questions

I'm hoping the community or Atlassian team can provide clarity on the following:

1. Domain Whitelist Expansion: Is there a process to request addition of custom domains to the Atlassian remote MCP server's redirect URI whitelist?

2. Future Roadmap: If custom domain whitelisting isn't currently supported, are there plans to implement this functionality? If so, what's the expected timeline?

3. Alternative Solutions: What workarounds exist for production deployments? For instance, is it feasible to self-host an Atlassian MCP server instance to bypass these restrictions?

Context

As an Atlassian customer, we're eager to incorporate the MCP server capabilities into our production workflows. Any insights, alternative approaches, or official guidance would be invaluable for moving forward with this integration .

Thank you for your expertise and support.

unknown

Hello @Zeeshan Parwez 

1. Is there a process to request addition of custom domains to the Atlassian remote MCP server's redirect URI whitelist?
   Nope

2. If custom domain whitelisting isn't currently supported, are there plans to implement this functionality? If so, what's the expected timeline?
   Nobody has created a feature request for it, so no timeline exists

3. What workarounds exist for production deployments? For instance, is it feasible to self-host an Atlassian MCP server instance to bypass these restrictions?
   No workarounds exist and you can't 'self host' it.

Refer to this thread on the Developer's forum on the same topic.

Hmmmm. And the original question on that thread contains sentences which are identical to your question. Other sentences are almost identical, except for some swapped nouns and verbs. Are you an AI bot @Zeeshan Parwez ?