Rovo MCP OAuth Consent Error – Missing Townsquare Scopes

[jackson gnanasekaran]

Hi,

I am trying to configure the Atlassian Rovo MCP server using the OAuth based setup, but the authorisation flow fails after authentication and site selection with the following error:

This app has requested scopes that have not been added to the app.

write:goal:townsquare

read:goal:townsquare

write:project:townsquare

read:project:townsquare

My understanding is that the OAuth application is requesting Townsquare (Goals/Atlas) scopes that are not configured on the app registration.

Has anyone else encountered this issue?

• Are these scopes expected to be present for the Rovo MCP integration?
• Is there a known workaround?
• Does this require an update to the Atlassian-managed OAuth application, or is there something that can be configured by the client?

Any guidance would be appreciated.

Thanks.

[Tomislav Tobijas · Accepted solution]

Hi @jackson gnanasekaran ,

It appears to be a widespread problem at the moment, as I've seen multiple questions about it 👀
I've tried checking the official status page, but I couldn't find anything reported: https://status.atlassian.com/ 😕

Can you or your admin reach out to Atlassian Support to report the issue? It might be that they are already aware, but they can probably give you additional insights around it.

Cheers,
Tobi

[Dr Valeri Colon _Connect Centric_]

@jackson gnanasekaran welcome to the community. I think your interpretation is on the right track. Atlassian already has ECO-1420 tracking the fact that the older *:townsquare Goals/Projects scopes aren't exposed through OAuth apps, Forge, or scoped API tokens.

If the Rovo MCP OAuth flow itself is requesting read/write:goal:townsquare and read/write:project:townsquare and then reporting that those scopes haven't been added to the app, I wouldn't try to fix this client-side. That points to the OAuth/MCP registration or scope configuration on Atlassian's side. I’d raise it with Atlassian Support and reference ECO-1420, including the exact consent error and MCP client you're using.