Add Rovo MCP scopes for service account API keys

XMLWordPrintable

      Problem

      search:rovo:mcp scope is not available for service account API keys. 

      This creates a gap between personal scoped API tokens and service account API keys for headless or machine-to-machine MCP use cases.

      Suggested Solution

      Expose Rovo MCP scopes, including at minimum search:rovo:mcp, in the service account API key creation flow so that service account credentials can be used with the same supported MCP toolsets as personal scoped API tokens where intended.

      Why This Is Important

      Customers using Atlassian Rovo MCP Server for non-interactive workloads often need to authenticate with a service identity rather than a personal user token.

      Without access to Rovo MCP scopes on service account API keys, customers cannot use service accounts for MCP search/fetch workflows

      Workaround

      Use a personal scoped API token instead of a service account API key

              Assignee:
              Unassigned
              Reporter:
              Simran G
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: