I’m building two Forge apps for Confluence that hold governance records in Forge SQL, and both are aiming for Runs on Atlassian. My customers want their own AI tools (Claude, ChatGPT, Copilot) to reach those records.
Two questions:
The rovo:mcp module shipped in Preview exposing actions to Rovo Studio agents. Is the external half of this RFC still planned, so that rovo:mcp tools become reachable from the Rovo MCP Server by external clients such as Claude Desktop? Is there a rough timeframe?
May a Marketplace app use a Teamwork Graph connector to feed its own Forge-stored records into the graph, and would doing so affect Runs on Atlassian eligibility?
Welcome to the Atlassian developer community @RichardLea,
Sorry, I realize your questions were related to RFC-134: Forge Rovo Tools and MCP
but I think we did a bad job closing that with a clear resolution.
Yes. Very close. I expect Dean’s original answer will still hold true and this should ship in September. Unless we find some very unpleasant surprises in our final “blitz” of testing.
Yes please and not necessarily. Yes, Teamwork Graph connectors are encouraged for Marketplace apps.
If I understand your case, you would just turn your Forge SQL records into Teamwork Graph objects. In that case, the app is still eligible for “Runs on Atlassian”. If your Teamwork Graph connector would require permissions.external.fetch.backend URL(s) in the manifest. Our research behind “Runs on Atlassian” indicated that customers prefer to keep their data on Atlassian unless there is a good reason like integration.
As a tangent, I don’t know if there’s a great object type to use. The set is currently pretty focused on Atlassian concepts. I’m tempted to suggest Test, in the sense that a governance policy is a “testable” assertion with results usually in the form of failure (success is assumed). But that’s probably “too clever”. A solid default is just Document.
Thanks Ian, that’s exactly what I needed on both counts. We’ll plan around rovo:mcp reaching external clients and test our Rovo actions through the Rovo MCP Server as soon as it lands, and I’ll take Document as the default object type if we build a connector. If you’re able to post here when the external access ships, I’d appreciate it.
Thanks Dean, that’s great news, and thanks for following up.
We don’t have Rovo actions in our apps yet, so we’ll add one and try it with Claude Desktop shortly. Two quick questions while we plan it:
Does a customer’s site need Rovo enabled for an external client to reach an app’s rovo:mcp tools, or does the OAuth connection work on any site with the app installed?
Is choosing which tools to expose (rather than the whole module as one group) planned before this leaves preview?
Hi Richard great to hear you will be trying it out!
No a customer’s site does not need Rovo enabled or licensed for an external AI client to access an app’s rovo:mcp tools. The OAuth connection works on any site where the app is installed as long as an admin has enabled “Expose tools via external MCP endpoint” (under Admin Hub → Connected Apps for that app).
Yeah having the ability to choose specific tools at an Admin level in the Connected apps area and the OAuth screen for the customer connecting is planned for GA.
Building on Dean’s answer about Rovo licensing, a few follow-up questions about shipping an app’s tools through rovo:mcp during the Preview:
Preview terms in production: what are the commitments during Preview: notice before breaking changes, support, availability, data residency? Can a customer rely on it in production?
The admin switch: “Expose tools via external MCP endpoint” is off by default per installation. Can the app detect whether it is on, so we can show admins a hint inside the app?
Identity and permissions: when an external client calls our tool, does the action run as the connected user with exactly their Jira permissions, as it does for Rovo?
Licence enforcement: is the app’s licence (active or lapsed) enforced on external calls the same way as inside Jira, and does our action receive the licence context?
Usage and billing: do external calls count toward our Forge usage the same way as calls from Rovo? Does the customer pay anything?
Requirements on the customer’s site: we understand from the community thread that the site needs no Rovo licence. Is that confirmed, and does it hold on every Jira Cloud plan, including Free and Standard?
Per-tool admin choice at GA: will that need any manifest change from us?
Atlassian’s own MCP Jira tools: can the entity-property read tool list an issue’s property keys, or does it need the key in advance? Is reading project properties planned? Some projects store a marker at project level, and assistants cannot reach it today.