rovo:mcp external endpoint returns "not allowed to expose its tools" when "Enable tools" is turned on while the app is connected to Jira + Confluence

Summary

For a Forge app with a rovo:mcp module that is installed on Jira and connected to Confluence, enabling
Connected apps → app → Details → TOOLS → Expose tools to MCP-compatible apps shows “Enabled” in Atlassian
Administration, but the external MCP endpoint (https://mcp.atlassian.com/forge/<appId>) still rejects
tool listing with:

App ari:cloud:ecosystem::app/<appId> is not allowed to expose its tools over the external MCP endpoint
on this site. An admin must enable external MCP access for this app.

If the same toggle is turned on while the installation is Jira-only, it works, and it keeps working after
Confluence is connected afterwards.

Environment

  • Forge CLI 14.2.0, runtime nodejs24.x
  • App: Jira (required) + Confluence (compatibility.confluence.required: false)
  • Modules: rovo:agent, 6 × action, rovo:mcp (5 tools), jira:projectPage, jira:issuePanel, macro
  • Environment: production (also reproduced in development)
  • MCP client: Claude Code (HTTP transport, OAuth via /mcp)
  • Reproduced with 2 different app IDs on the same site (Rovo Enterprise). The working order (Jira-only → enable tools → connect Confluence) was confirmed on a second site in another organization (Free plan)

Steps to reproduce

  1. Deploy a Forge app with a rovo:mcp module and Confluence as an optional compatible product.
  2. Install it on a site for Jira and Confluence (forge install --product jira, then --product confluence).
  3. In Atlassian Administration → Apps → Sites → site → Connected apps → app → Details (?product=jira),
    click Enable tools. The page shows “Expose tools to MCP-compatible apps: Enabled”.
  4. In the MCP client, add https://mcp.atlassian.com/forge/<appId> and authenticate (consent screen shows the correct site).
  5. List tools.

Expected: the app’s tools are listed.
Actual: the connection succeeds but the tool fetch fails with the error above. Capabilities: none.

What did NOT help

  • Re-authenticating and selecting the site again on the consent screen
  • Switching from the development to the production environment
  • Changing distribution to “Sharing within organization”
  • Disable → Enable tools while Confluence is still connected
  • Registering a brand-new app ID (forge register) with the same manifest

Workaround (works every time)

  1. Remove the Confluence connection (forge uninstall --product confluence, or Connections → Disconnect).
  2. Connected apps → app → Details → Disable tools, then Enable tools again.
  3. The MCP client now lists the tools.
  4. Connect Confluence again. The tools keep working.

Alternatively, install Jira only, enable tools first, then connect Confluence.

Questions

  1. Is enabling external MCP exposure expected to depend on which products the installation is connected to at the time of enabling?
  2. Can the admin UI show the real exposure state, or the docs mention this ordering requirement?

Happy to share app IDs / timestamps privately if useful.

Seeing this too and it’s not clear if its intended behaviour or a bug

CC @DeanPeach

Hi @BayuTrisnapati thanks for raising this. This does appear to be unintended behaviour for a cross context apps with the rovo:mcp module. We have identified the root cause and are rolling out a fix for it. We’ll get it out asap. We appreciate you sharing this with us.

Cheers,

Dylan