We're running into an issue performing Rovo Search through the Claude Atlassian Rovo connector. Other MCP calls (e.g., searchJiraIssuesUsingJql) work as expected, but Rovo Search specifically fails.
We have an open ticket with Atlassian Support, and they've confirmed the calls are returning a 403 error. They're currently investigating further on their end.
For context on our setup:
Has anyone else run into this? Curious whether other teams are seeing the same 403 on Rovo Search via Claude specifically, and if so, whether you found a workaround or root cause on your side. I'll post an update here once Atlassian Support gets back to us with more information or a fix.
Thank you for posting this and good to know it is already in safe hands with Atlassian support. Do post here what they diagnosed and the fix provided.
Hi, @Viswanathan Ramachandran!
Thanks for your response.
I've tried re-authenticating the connector multiple times, and each time I've made sure that Search operations are enabled during the authorization process. Our whole org is affected at this point.
I'm also only using the allowlist for the whole Rovo MCP server, with the Claude and ChatGPT URLs included in the allowlist.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Similar thread - https://community.atlassian.com/forums/Atlassian-Remote-MCP-Server/atlassian-searchJiraIssuesUsingJql-server-side-validation-issue/td-p/3262391
did you hear from Atlassian?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.