Jira Remote MCP Server in Copilot Studio

[Simon Kolivand]

Hi,

I’ve been experimenting with the Jira MCP server in Copilot Studio and successfully created an agent that’s connected to our Jira site. I can use prompts like CreateIssue to create issues, GetCurrentUser to retrieve information about my user, and ListProjects to view all of my Jira projects.

However, whenever I try to use other prompts or ask more specific questions, I encounter the following error:

Error Message: The output returned from the connector was too large to be handled by the agent. Try reducing its size by utilizing available connector filters or by limiting the number of configured action outputs. Error Code: AsyncResponsePayloadTooLarge

Has anyone found a way to resolve this error, or tips on how best to leverage the Atlassian Remote MCP server?

Best regards

Simon

I've attached my current Tools within the Agent:

[Tomislav Tobijas · Accepted solution]

Hi @Simon Kolivand ,

I can't help much with this, but I'm going to move it to the Rovo group as there are some people who might be able to assist.
Btw, as of this morning, they renamed it to Atlassian Rovo MCP Server > announcement here.

Cheers,
Tobi

[Simon Kolivand]

Hi Tobijas,

Thank you for your answer. I'm not interested in the connection to Rovo since we aren't using it. I'm specifically interested in setting up the Jira MCP with Copilot as mentioned in the article that I referenced. 

Could you please move my question back so it's not relocated in Rovo questions.

Thanks in advance

Simon

[Tomislav Tobijas]

Got it @Simon Kolivand 

There's a forum group for MCP Server > link here. As I'm not exactly sure where this question should land 'by the book', so I've reached out to the team to confirm.

It's not ideal, but you could also create a separate discussion within the mentioned group. 👀

Anyway, I'll throw an update here as soon as I get back info from the product team.

[Simon Kolivand]

Hi Tomislav,

Appreciate it! Have a great day.

[Dr Valeri Colon _Connect Centric_]

@Simon Kolivand That error isn’t from Jira—it’s a Copilot Studio limit. The Atlassian MCP server returns full Jira payloads, and Copilot drops anything over its response-size cap, which triggers AsyncResponsePayloadTooLarge. There’s no fix yet. The only workaround is narrowing the MCP call (smaller JQL, specific fields, fewer projects). Until Microsoft raises the limit, large Jira responses won’t work through Copilot.

[Simon Kolivand]

Hi,

Appreciate the answer! I figured that it was a Copilot Studio limit but the issue still occurs no matter how specific I am. Even if I narrow my call down to 1 specific field in 1 specific project I still get the same error.

[Wouter Dumon]

Hey, were you ever able to find a solution to this?

[Simon Kolivand]

Hi Wouter,

Sure did - I found another and better way to set it up. I've created an agent in Copilot Studio and connected it to the Jira MCP server. I then added copilot as an approved domain within atlassian admin. I do have some minor issues like it not being able to read custom fields or sprints but other than that I got it to work. I'll be working on it and as soon as it's working as intended and the quality is there, I will be sharing it with my org. I might make a post on Forums just to share if it has any interests.

Best regards

Simon