Hi everyone,
I'm trying to integrate the Atlassian Remote MCP Server with a third-party MCP client and I'm looking for some clarification regarding official support and OAuth configuration.
According to the documentation, the server exposes:
MCP endpoint: https://mcp.atlassian.com/v1/mcp/auth
Authorization endpoint: https://mcp.atlassian.com/v1/authorize
Token endpoint: https://cf.mcp.atlassian.com/v1/token
Registration endpoint: https://cf.mcp.atlassian.com/v1/register
When configuring the MCP server in Microsoft Copilot Studio, the connection fails during Dynamic Client Registration with the following error:
Failed to login.
GetDynamicClientRegistrationResultAsync failed.
Status Code: Unauthorized
{
"error": "invalid_token",
"error_description": "Missing or invalid access token"
}I'd like to understand whether this is an expected behavior or if I'm missing any required configuration.
My questions are:
Is Microsoft Copilot Studio officially supported as an MCP client for the Atlassian Remote MCP Server?
Does the https://cf.mcp.atlassian.com/v1/register endpoint support Dynamic Client Registration (RFC 7591) for external clients?
Is there any additional authentication or registration step required before calling the registration endpoint?
Should new integrations use /v1/mcp/auth or /v1/mcp/authv2?
Has anyone successfully connected Microsoft Copilot Studio (or another MCP client using OAuth/DCR) to the Atlassian Remote MCP Server?
Any guidance or working examples would be greatly appreciated.
Thanks!
Welcome to the community.
This seems like an issue on the MS side,as this is mentionedin other post as well.
It seems to relate to, that Microsoft Copilot Studio, can't handle that Atlassian MCP has upgraded their OpenApi specification to V3 which is not supported in Copilot Studio.
Also check this post on this topic; Microsoft-Copilot-Studio-Rovo-MCP-tools-no-longer-discovered
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.