using tool createJiraIssue and receiving status 200 with error ""We are having trouble completing

[Aditya Raman]

using tool createJiraIssue and receiving status 200 with message ""We are having trouble completing
cloudI Id tried with uuid and https://<>.aylassian.net
Also tried other tools .. I am getting same response.. Is it permission scope issue or something else??

[Arkadiusz Wroblewski]

Hello and Welcome to the Community @Aditya Raman 

To narrow this down, do read-only tools like listing projects work, or are all MCP tools failing? If it is a total connection failure, we are likely looking at an auth or permission blocker has your Org Admin explicitly enabled write access for the Rovo MCP server?

On the other hand, if only createJiraIssue fails, can your user account manually create that exact issue type in the target project, and have you tried testing a bare-minimum payload with just the project key, issue type, and summary to rule out hidden required fields?

[Tomislav Tobijas]

Hey @Aditya Raman ,

Can you maybe share a bit more detail about this integration through MCP that you're trying to create?

Also, have you followed the instructions from the official support docs: Getting started with the Atlassian Rovo MCP Server 
Specifically, this relates to auth. and authorization: Authentication and authorization 

I cannot convert/move this question there, but here's a discussion group specifically related to MCP Server, so I'd recommend checking that. 👀

Cheers,
Tobi

[Aditya Raman]

Thanks for the pointers. I know I am using sse but its active supposed to be sunset by June 

This does not appear to be an authorization/connectivity failure at the MCP connection layer. The proxy successfully authenticates and connects to Atlassian MCP:

HTTP Request: GET https://mcp.atlassian.com/v1/sse "HTTP/1.1 200 OK"
✓ Connected to Atlassian MCP server

The tool call is also accepted by the Atlassian MCP endpoint:

POST https://mcp.atlassian.com/v1/sse?... "HTTP/1.1 202 Accepted"
✓ Tool executed successfully

The same generic response occurs not only for createJiraIssue, but also for read-only metadata tools such as getJiraProjectIssueTypesMetadata. So this is not limited to hidden required fields on createJiraIssue.

The JSON-RPC response is HTTP 200, with isError: false, but the tool content contains:

{"error":true,"message":"We are having trouble completing this action. Please try again shortly."}

So the issue seems to be an application-level/tool-level failure returned inside the MCP response body, rather than a transport-level authorization error.

We have also tested the bare-minimum create payload with only cloudId, projectKey, issueTypeName, and summary, and it returns the same generic error.