Connect Atlassian Jira Remote MCP to Copilot Studio
Diesen Beitrag auf Deutsch lesen
Use Dynamic discovery, enable Atlassian prerequisites, create the environment connection, verify with JQL, and publish the agent.
TL;DR
Atlassian Remote MCP uses RFC 7591 Dynamic Client Registration, so Copilot Studio must use Dynamic discovery rather than Manual OAuth. Enable Atlassian Cloud, Rovo, Remote MCP, external app access, and product access first. Then create the MCP tool, consent, activate the connection, select Add and configure, verify with JQL, and publish.
Original by Hazim SharafelDin, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: select Dynamic discovery for the Atlassian MCP tool and complete Add and configure, because creating the connection alone does not attach it to the agent.
- Admins/CoE: keep the Atlassian prerequisites enabled and protect the environment connection, because deleting it can silently break every agent using it.
- Security/Compliance: review external app policies and user consent requirements, because strict enterprise policies may block the Atlassian MCP client.
Frequently asked questions
How do I authenticate Atlassian Remote MCP in Copilot Studio?
Use Dynamic discovery because Atlassian uses RFC 7591 Dynamic Client Registration instead of a pre-registered OAuth client.
Which Atlassian settings must be enabled before adding Jira to Copilot Studio?
Enable Atlassian Cloud, Rovo, Remote MCP, external app access, and the user's Jira or Confluence product access before connecting.
Why does an Atlassian MCP connection in Copilot Studio return 401 errors later?
Manual OAuth can pass consent but fail during refresh because Atlassian has no static client. Dynamic discovery handles the runtime registration.