API Scopes dont exist

[Wil Jones]

Some of the scopes detailed on this page https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/

Don't exist when creating an API token. I want to use rovo mcp via a service account and an API token but I can't see the scopes to configure it properly.

[Gor Greyan]

Hi @Wil Jones

Welcome to the Atlassian Community!

I found this suggestion/feature request to support Rovo-specific scopes for service account API keys. I think this is the case.

https://jira.atlassian.com/browse/AX-1938

[Arkadiusz Wroblewski]

Hello and Welcome to Community @Wil Jones 

Which Scopes for example ?

Some scopes won´t be exposed for Service Accounts and need another form of Authentification. This is still Evolving process.

Best,

Arek🤠

[Wil Jones]

For example this scope isnt there search:rovo:mcp

[Arkadiusz Wroblewski]

That is probably a current limitation. Service accounts do not have access to every endpoint or scope, so some functionality may require a different authentication method.

Again everything around Rovo evolving so that can change fast.

[Gabriela]

Hi @Wil Jones, Arkadiusz and Gor are right that it's a current limitation, and AX-1938 is the ticket that maps to it exactly. The Rovo search scopes (`search:rovo:mcp` is the one you flagged) aren't offered when an admin generates a service-account API key right now, so you're not missing a step in the console.

Per that ticket those same scopes are selectable on a scoped personal API token and over OAuth 2.1; the service-account key is the one path that doesn't expose them yet. So creating a scoped personal token and hand-picking the Rovo MCP scopes is the stopgap that gets Rovo Search running non-interactively today, under that user's identity, until service accounts catch up. AX-1938 is in Gathering Interest, so vote and watch it to push for the service-account support.