Microsoft Copilot Studio - Rovo MCP tools no longer discovered

[Jake Cherrie]

I’ve been using the Atlassian Rovo MCP Server with Microsoft Copilot Studio via a custom MCP connector. This was working fine over the past couple of weeks, but earlier today it suddenly stopped discovering tools in Copilot Studio. Has anyone else been using the Rovo MCP in Copilot Studio and experienced similar issues?

Copilot Studio is configured with Microsoft’s current MCP streamable connector marker: `x-ms-agentic-protocol: mcp-streamable-1.0`

The connector creates/authenticates successfully, but the tool list now shows: `No tools available`

A few control tests:

- The same Rovo MCP connection still works in Claude Code, where tools are visible and callable.

- Other MCPs with custom connectors works in the same Copilot Studio environment.

- I’ve tried recreating the connector, using another Power Platform environment, and testing both `/v1/mcp` and `/v1/mcp/authv2`.

One possible clue: Microsoft’s Copilot Studio MCP troubleshooting docs list several current MCP schema limitations, including issues with integer `exclusiveMinimum` values, multi-type schemas, reference-type inputs/outputs, and enum handling.

[Jess G]

We're experiencing the same issue. The Rovo MCP Server connection in Copilot Studio initializes successfully and shows status "Working," but the tools list comes back empty - "No tools available."

When we try to actually use the agent, it throws a SystemError at runtime. So it's not just a UI issue with tool discovery, the agent can't function at all.

We also tried creating a completely new connection using the /v1/mcp/authv2 endpoint with the same result. Connection authenticates fine, but no tools are returned.

We've submitted a support ticket to Atlassian with screenshots and the error details. Would love to hear if the Rovo team or anyone else has updates, especially whether Atlassian and Microsoft are coordinating on this.

[Robin]

Hi,

Any updates on this? Our team has the same issue and I was wondering if there was any further feedback.

Is it possible to share the ticket or is that not publicly available?

Thanks!

[Jess G]

Hi Robin, Atlassian is taking a look and I am sending them our troubleshooting steps but no updates just yet. If they make a public bug ticket for this I will share it out. I will keep this thread udpated as we work through this with Atlassian.

[Sree Nerella]

Thank you for reporting this. We have been investigating similar reports regarding Microsoft Copilot Studio and the Atlassian Rovo MCP Server.

Based on our initial findings, this issue appears to be isolated to the Microsoft Copilot Studio client. Our team has tested the MCP server with other clients and has been unable to reproduce the discovery failure elsewhere. However, we have confirmed that the issue does occur within the Microsoft environment.

Recommended Next Steps:

1. We recommend reaching out to your Microsoft Studio Partners or support team in parallel to investigate potential client-side changes or configurations on their end.

2. On our side, we are currently working with our Partnership team to raise a formal bug report with Microsoft to help expedite a resolution.

We will provide further updates as we learn more from the Microsoft team

[Jake Cherrie]

I’ve raised this with Microsoft as well - will post any updates here if/when I get more information.

[Sree Nerella]

Thank you @Jake Cherrie 

[Sree Nerella]

Thank you for reporting this. We have been investigating similar reports regarding Microsoft Copilot Studio and the Atlassian Rovo MCP Server.

Based on our initial findings, this issue appears to be isolated to the Microsoft Copilot Studio client. Our team has tested the MCP server with other clients and has been unable to reproduce the discovery failure elsewhere. However, we have confirmed that the issue does occur within the Microsoft environment.

Recommended Next Steps:

1. We recommend reaching out to your Microsoft Studio Partners or support team in parallel to investigate potential client-side changes or configurations on their end.

2. On our side, we are currently working with our Partnership team to raise a formal bug report with Microsoft to help expedite a resolution.

We will provide further updates as we learn more from the Microsoft team

[Jake Cherrie]

Thanks for the update - really useful context.

One question from our side: do you know if there have been any recent changes to the MCP tool schema returned by the /v1/mcp or /v1/mcp/authv2 endpoints?

Given that the same Rovo MCP is still working in other clients (e.g. Claude), I’m wondering whether a schema change, even if valid per MCP, might now include constructs that Copilot Studio doesn’t currently support, leading to tools not being discovered.

[Paul Huang]

Hi, I have got the following reply from Microsoft Copilot Studio Engineer: Atlassian MCP has upgraded their OpenApi specification to V3 which is not supported in Copilot Studio. May I ask confirm from your side about this?

[Jake Cherrie]

Thanks Paul - really helpful to know. I’m still waiting to hear back from Microsoft on my end, but I’ll pass this on.

I don't suppose the Copilot Studio engineer mentioned whether support for OpenAPI v3 is on their roadmap or planned for a future release?

[Paul Huang]

They replied that the product team from MS will implement a fix for this early June.