Rovo MCP Server: Return clear, actionable error when a token/request is missing orgId/cloudId (instead of generic "trouble completing this action")

XMLWordPrintable

      Problem

      When connecting to the Atlassian Rovo MCP Server (https://mcp.atlassian.com/v1/mcp) with a raw HTTP client (e.g., Postman) or a non-standard MCP client, requests that are missing required context, such as orgId (for policy enforcement) or a valid cloudId/redirectUri, fail with a generic, non-actionable error:

      "We are having trouble completing this action."

      The response does not indicate what is missing or how to fix it. There is no hint that the token lacks orgId, or that a valid cloudId / registered redirectUri is required.

              Assignee:
              Unassigned
              Reporter:
              Diego Larangeira
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: