Rovo MCP Tool Execution Fails with Generic Error During OAuth Authentication

Summary

When using an MCP client (e.g., n8n, Postman) to connect to the Atlassian Rovo MCP server, tool discovery (tools/list) and identity queries succeed, but executing specific Jira tools (e.g., getJiraIssue) fails with a generic error message.

Diagnosis

• MCP session initializes successfully.

• tools/list returns the expected list of tools.

• Executing a tool returns the following error: {"error":true,"message":"We are having trouble completing this action. Please try again shortly."}

• The issue persists across both standard (/v1/mcp) and authv2 (/v1/mcp/authv2) endpoints.

Cause

The failure is typically caused by using a standard OAuth 2.0 3LO (Three-Legged OAuth) flow that lacks required parameters like orgId and redirectUri. Internal policy enforcement blocks tool execution when these identifiers are missing from the integration context.

Solution

To resolve this, ensure the MCP client uses OAuth 2.1 with Dynamic Client Registration (DCR). This ensures that the orgId and redirectUri are correctly passed and validated during the tool execution request.

Steps to Fix:

1. Verify Authentication Flow: Ensure your client is configured for OAuth 2.1.

2. Check Redirect URI: Confirm that a valid redirectUri is present in the authentication request.

3. Consult Documentation: Refer to the following guides for specific configuration requirements:

   • Authentication and authorization

   • Use Atlassian Rovo MCP Server

   • Configure Atlassian Rovo MCP server permission