Developer
News and Updates
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Last updated Jul 22, 2026

Selecting API token scopes for the Preview endpoint

When you connect to the Atlassian Rovo MCP Preview endpoint using an API token, the token must carry the correct scopes. The Preview endpoint uses a new set of scopes (the agent-interface scopes), which differ from the scopes used by the generally available (GA) endpoint.

Preview (v2) scopes

Use this set when creating a token for the Preview endpoint (https://mcp.atlassian.com/v1/mcp/preview).

Use the following link to open the token creation screen with the Preview scopes pre-selected:

Create a token with Preview scopes

The Preview scope set includes:

ProductScopes
Jiraread:jira:agent-interface, write:jira:agent-interface, search:jira:agent-interface
Confluenceread:confluence:agent-interface, write:confluence:agent-interface, search:confluence:agent-interface
Rovo Searchsearch:rovo:agent-interface
Loomread:loom:agent-interface, write:loom:agent-interface

Using the generally available endpoint

If you're connecting to the GA endpoint (https://mcp.atlassian.com/v1/mcp) instead, use the classic product scopes rather than the Preview scopes. See Configuring authentication via API token for the GA scope set.

Troubleshooting

Tool calls fail with a permission or scope error

Your token may be missing a required scope, or may be using the GA scopes against the Preview endpoint (or vice versa). Recreate the token with the set that matches your endpoint.

Share feedback

The Preview endpoint will evolve. If you hit a bug or have feedback on scopes, post in the Atlassian Rovo MCP Server community.

Rate this page: