Unable to enable Atlassian Rovo MCP Server - API Token

Kintur Shah

Hi,
I am unable to add enable toggle for the API Token for Atlassian, my admin tried opening that page and every time it says, something went wrong. For my application, I wanted to use ROVO MCP Server and I am facing issues to access this now, initially it worked but I don't know it's not working now, and I want to raise a ticket as well so that Atlassian Support can help me resolve this use, please guide me through any workable solutions or any link to raise a support ticket.

Thanks

Alexandre Pezzini

The "Something went wrong" error when trying to enable the API Token toggle for the Atlassian Rovo MCP Server is often related to a permissions or session conflict in the Atlassian Administration panel.

Since you are looking to use the ROVO MCP Server and need to resolve this to raise a support ticket, here are the recommended steps:

1. Verify Admin Permissions

To toggle this setting, your admin must have Organization Admin permissions. Even if they are a Site Admin, certain Rovo and MCP settings require the higher-level Organization Admin role.

• Path to check: Atlassian Administration > Rovo > Rovo MCP server > Authentication.

2. Troubleshooting the "Something went wrong" Error

This error is frequently a transient UI issue. Ask your admin to try the following:

• Incognito/Private Mode: This rules out browser cache or conflicting cookies from other Atlassian sessions.

• Check for IP Allowlisting: If your organization uses IP allowlisting, the admin's current IP must be on the allowlist to modify these security settings. If the admin is on a VPN, they should try toggling it while disconnected (if permitted by company policy).

• Verify Rovo Subscription: Ensure that the Atlassian Rovo subscription is active and not in a "Suspended" or "Pending" state, as this can lock the configuration toggles.

3. How to Raise a Support Ticket

If the toggle still won't enable, you should raise a technical support ticket. Since you are having trouble accessing the standard path, use this direct link:

• Support Link: Atlassian Support

• Details to include:

  • The specific URL where the error occurs (e.g., admin.atlassian.com/o/<org-id>/rovo/mcp-server).

  • A screenshot of the "Something went wrong" message.

  • Confirmation that the user attempting the change is an Organization Admin.

4. Alternative: Use OAuth 2.1

If the API Token toggle remains stuck, remember that the Rovo MCP Server also supports OAuth 2.1, which is the recommended authentication method for interactive clients like Claude Desktop or VS Code.

• OAuth does not require this specific "API Token" toggle to be enabled; it only requires the admin to authorize the app during the first connection.

Reference Documentation:

• Control Atlassian Rovo MCP server settings | Atlassian Support

• Configuring authentication via API token | Atlassian Rovo MCP Server Cloud | Atlassian Support