Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft Copilot Studio - Rovo MCP tools no longer discovered

Jake Cherrie
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 11, 2026
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.

1 comment

Comment

Log in or Sign up to comment
Jess G
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 12, 2026

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.

Like Jake Cherrie likes this
Robin
May 13, 2026

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!

TAGS
AUG Leaders

Atlassian Community Events