Atlassian Rovo MCP Server to add to Copilot Studio Agent

(2) Share

Report

Posted on by FD-02100459-0

This should be a common MCP Server to be used, see also https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/

I went through the steps to add a tool (of type MCP Server) to my Copilot Studio Agent.

This remote MCP server works exclusively with OAuth, so I selected OAuth and tried to provide the correct details (referring to an OAuth 2.0 app I had to define at developer.atlassian.com).

After creating the MCP Server, it failed to add itself to the Agent. I can still see it in the tools, and try to add it again, but the buttons to "Add to Agent" or "Add and configure" are greyed out.

It would be useful to have this in the Features List of MCP Server with some built-in OAuth config. It takes zero OAuth config to add this to e.g. VS Code or Claude Desktop.

Categories:

Model context protocol

I have the same question (7)

All responses (2)

Answers (0)

Sort by

Suggested answer

DAnny3211 138 on at

Like (0)

Report
Copy link

Link copied!
Hi, Thanks for sharing the details and the link to the Atlassian documentation. Based on your description, it seems the issue may be related to how Copilot Studio currently handles OAuth-based MCP Server integrations. At the moment, Copilot Studio does not support automatic configuration of third-party tools like the Atlassian Rovo MCP Server with built-in OAuth flows. Unlike environments such as VS Code or Claude Desktop, where OAuth integration is streamlined, Copilot Studio requires manual setup and may not yet fully support all external OAuth configurations—especially for tools not listed in its native feature set. The greyed-out “Add to agent” and “Add and configure” buttons suggest that the tool was registered but not validated or authorized correctly. This could be due to missing scopes, redirect URI mismatches, or limitations in the current preview version of Copilot Studio. You might find additional guidance in the official documentation for tool integration in Copilot Studio: - Add tools to Copilot Studio agents - OAuth setup for external tools If the issue persists, consider raising a support ticket or sharing feedback directly through the Copilot Studio interface to highlight the need for built-in OAuth templates for common MCP Servers. Thanks and best regards, Daniele *Note: This response was prepared with support from Copilot to ensure clarity and completeness.*

Was this reply helpful? Yes No
KK-29091652-0 32 on at

Like (0)

Report
Copy link

Link copied!

Hi FD-02100459-0,

I'm trying to integrate the Rovo MCP server with a custom Copilot Studio agent as well.

Would you be able to share how you approached this integration or point me to any documentation you followed?

I’d love to give it a try and perhaps we can exchange insights later.

Cheers

Was this reply helpful? Yes No