Overview

Atlassian Service Accounts currently do not support the generation of API tokens with specialized Rovo scopes, such as "search:rovo:mcp" and "search:rovodev". This prevents automated systems using service accounts from interacting with Rovo-specific endpoints.

Current Process

Rovo API scopes are currently only available when using Personal API Tokens from regular user accounts or through specific OAuth 2.1 flows, rather than via Service Account tokens.

Feature Request

We would like the ability to select and authorize Rovo-specific scopes ("search:rovo:mcp" and "search:rovodev") when creating or managing API tokens for Atlassian Service Accounts.