Cloud site: moveinsync.atlassian.net (cloudId a6e123b0-3842-4bc0-b88a-8a83e1c5458f)
We're integrating an internal app with the Atlassian Rovo MCP server to run semantic Jira search. The "search" tool is exposed when we connect over OAuth, but
every call to it fails with:
403 — "You don't have permission to search content. Please contact your administrator to request access. Details: { code: 403, message: 'The app is not
installed on this instance' }"
What we've already verified:
- Rovo search works fine in the Jira UI for our user (nipin.mishra@moveinsync.com).
- Connected via OAuth (mcp-remote) with a freshly issued token — the "search" and "fetch" tools ARE listed, but calling "search" returns the 403 above.
- Re-authenticating with a fresh token gives the same 403 (so it's not a stale token).
- Rovo MCP server settings: Permissions → Search = ALLOWED; Authentication → API token = ON; Domains → supported domains allowed.
- Admin → Rovo → "Rovo access" shows that choosing which apps/groups can use Rovo requires a paid plan, and it is currently not configured.
Questions:
1. What Rovo plan/entitlement is required so that an APP (not just a UI user) can call the Rovo MCP "search" tool?
2. What does "The app is not installed on this instance" mean here, and how do we install/provision Rovo Search for apps on our instance?
3. Is OAuth required (vs API token), and does the search tool need anything beyond the "Search" permission group being ALLOWED?
Goal: be able to call the Rovo MCP "search" tool programmatically to fetch semantically-relevant Jira tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.