Connecting Lovable with Atlassian MCP

[Joel Järvela]

I am trying connect Lovable to Confluence. From lovable, I try to do the connection, and I am getting error 

Your organization admin must authorize access from a domain to this site.

Contact your organization admin to authorize access from domain api.lovable.dev to site estvest.atlassian.net.

However, I have enabled lovable in my Confluence site

Does anyone know what am I still missing?

[Raul Pelaez · Accepted solution]

For the error message:

- Your organization admin must authorize access from a domain to this site.
Contact your organization admin to authorize access from domain api.lovable.dev to site yourcompany.atlassian.net.

The solution is here: 

Add domains
You can add domains you trust to enable integrations with specific AI tools.

To add a domain:

Go to Atlassian Administration. Select your organization if you have more than one.

Select Apps > AI settings > Rovo MCP server.

Select Add domain.

How to format domain URLs

[Raul Pelaez]

Here a video of the integration working in Lovable through Atlassian MCP

https://youtu.be/QiFfCKnae3g

[Raul Pelaez]

Finally, the Atlassian Connector in Lovable doesn't work fine, verified. I disconnect it.

The best option is to configure the MCP extension in Lovable and put the new URL for the Atlassian MCP https://mcp.atlassian.com/v1/mcp

It works perfectly 

[Raul Pelaez]

Here more info: https://support.atlassian.com/security-and-access-policies/docs/available-atlassian-rovo-mcp-server-domains/

[Giorgi Gvimradze]

recommended allowlist, I've tried few different names but finally just added the all possible ways:

https://www.cursor.com

https://cursor.com

https://*.cursor.com

https://cursor.sh

https://*.cursor.sh

https://app.cursor.sh

[Giorgi Gvimradze]

retried the whole login and authorization from cursor agents mcp but didn't wor. will try to log in and out, maybe a token is the thing

[Giorgi Gvimradze]

still didn't work for me. 

[Tomislav Tobijas]

Hey @Joel Järvela ,

Even after allowing a domain (which seems to be correct in this case; incl. wildcard use), the integration must still complete the OAuth 2.1 authorization flow. This requires the correct scopes and user permissions > more on that here: Authentication and authorization 👈
Note that the use attempting the connection must have product/app access to Confluence and, and the authorization must inherit those permissions.

There's also this feature request related to delegated authorization: AI-1194: Delegated Authorization for Rovo Integrations with Third-Party Systems (e.g., ServiceNow, Microsoft 365) – No Cross-System Admin Required as there are still some known limitations around this and allowlisting third-party domains for integrations like MCP server. 👀

Cheers,
Tobi

[Trudy Claspill]

Hello @Joel Järvela 

Disclaimer: I have not worked with Rovo MCP server setups.

Did you know there's a dedicated group for MCP server questions/discussions where you might get better help?

 Atlassian Rovo MCP Server 

Has your Organization defined any restrictions through IP Allowlist?