Issue with OAuth Redirect URI Whitelisting for Atlassian Remote MCP Server

Atlassian Developer Tools
1

Hi Atlassian Community

I’m trying to integrate the Atlassian remote MCP server’s OAuth flow in a self hosted external application and I’m encountering a persistent issue that is preventing successful authorization redirects.

After successfully registering a client and then directing a user to the authorize endpoint, I consistently receive the following error response: "The redirect URI is not allowed, the URL is not part of Atlassian whitelisted domains for registered MCP Clients. Redirect URI <my_redirect_uri>".

After looking around in forums and blog posts, it appears the Atlassian remote MCP server might have a very limited whitelist that primarily includes some IDE’s, Claude tools and localhost for a local development environment, which is why my integration works perfectly within a local development environment, but not on a self hosted external application behind our own domain.

Questions:

  1. Is it possible to add our own domains to the whitelist of the Atlassian remote MCP server?
  2. If not possible at this moment, are there plans to enable this in the future, and is there an estimate on when this would happen?
  3. In the meantime, is there any workaround or alternative approach for integrating the Atlassian remote MCP server’s OAuth flow in a self hosted external application behind our own domain? Can we host an Atlassian MCP server ourself for example?

We are a paying customer using Atlassian products, and we would love to integrate the Atlassian remote MCP server in our workflow. Any guidance or clarification around this topic would be greatly appreciated!

Thank you for your time and assistance.

Kind regards

21 Likes
2

I ran into the exactly same error message and wondering about those three questions mentioned above as well. @AtlassianSupport I would really appreciate it if someone can answer these questions. Thank you.

4 Likes
3

Having the same issue. Would love a way to add our domain!

2 Likes
4

Agreed, the Jira MCP server is not useful for us unless we can use our domain.

5 Likes
5

When are we going to have custom domain callback?

4 Likes
6

Also blocked by this error. @AtlassianSupport when can we add our own custom domain as an authorized redirect URI for MCP server integration? Is this something that our Atlassian rep can assist with?

1 Like
7

Without this, building ontop of the MCP capability is rather limited. It would be great if a registered callback via the atlassian console could add these callbacks to the whitelist.

4 Likes
8

This is a blocker for us. Would be ideal if we could add our own domains to the whitelist.

9

Same issue. And this is for an app in the Apple App store

10

We also have this issue when trying to use a MCP Gateway

11

Unusable til we have a way to custom redirect uri’s. Atlassian your customers need help.

12

We need this as well!

13

Hello. We also need to resolve this. We want to integrat Atlassian into Cursor over MCP and are getting: “The redirect URI is not allowed, the URL is not part of Atlassian allowlisted domains for registered MCP Clients. Redirect URI cursor://anysphere.cursor-mcp/oauth/user-atlassian-mcp-server/callback“

14

We need this, too.

15

Also blocked by this when trying to connect in Cursor. Everything worked fine until 2 days ago, now it’s not on allowlist anymore.
This is going for months now with no help @AtlassianSupport

16

OpenWebUI enabled to connect to MCP like this, but it’s blocked by the whitelist. It would be great if there is any progress @AtlassianSupport