MCP server only working with Rovo Dev License?

[Johannes Modersohn]

Hi there,

we used to be able to use the MCP server and were able to access Jira and Confluence. However since a while the connection is broken. After the license change of the Rovo Dev Agent it seems MCP server is only working, when you have licensed the Rovo dev agent. Is this right? Or should it be working via the regular Rovo accessibility? There is nowwhere anything documented in the MCP documentation, so I am a bit frustrated about the uncertainty.

Thanks in advance for clarification. 

BR,
Johannes

[Dr Valeri Colon _Connect Centric_ · Accepted solution]

Welcome to the community @Johannes Modersohn  Rovo MCP should still work for general Jira/Confluence access, but some MCP features now depend on having Rovo Dev licensed because the same backend powers both. If your org lost Rovo Dev credits or licensing, MCP calls that require dev-level actions can fail even though basic Rovo is enabled. Atlassian hasn’t documented this clearly yet. If you previously had MCP access and it stopped after the licensing change, open a Support ticket—this can happen when your site is no longer flagged for Rovo Dev entitlement.