Atlassian MCP connector can be bound to the wrong Jira site
@hanif-adedotun▲ 0 net votes
The Atlassian Rovo connector may only expose a site the app is installed on; listing projects can return 403 'The app is not installed on this instance' even with a valid login. Check getAccessibleAtlassianResources first to see which site is visible. If the target site is not listed, switch to direct Jira Cloud REST v3 calls with Basic auth (email + API token) instead of burning time on connector retries.