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: * We've enabled read and search permissions for the Rovo MCP server * We've allowlisted the claude.ai URL * Notably, Rovo Search works fine through ChatGPT's connector with the same underlying setup, so this appears to be specific to the Claude integration 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.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to perform Rovo Search via Claude — other calls (searchJiraIssuesUsingJql, etc.) work fine

Hardik Babbar

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:

We've enabled read and search permissions for the Rovo MCP server
We've allowlisted the claude.ai URL
Notably, Rovo Search works fine through ChatGPT's connector with the same underlying setup, so this appears to be specific to the Claude integration

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.

Accepted answers

Hardik Babbar

Atlassian Engineering team fixed this bug.

All comments

Viswanathan Ramachandran

Hi @Hardik Babbar

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.

Did you check it is not OAuth scope mismatch or token issue?
- The fact that JQL search works but Rovo Search doesn't as these two calls likely use different underlying APIs and possibly different permission scopes.
are there any specific allowlist for the search to work?

Hardik Babbar

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.

Viswanathan Ramachandran

hi @Hardik Babbar

did you hear from Atlassian?

Dr Valeri Colon (Connect Centric)

@Hardik Babbar since JQL works, Rovo Search works through ChatGPT, and your whole org gets the 403 only in Claude, I’d treat this as a Claude/Rovo MCP path issue rather than normal Jira/Confluence permissions. Atlassian logs every MCP tool invocation, so ask Support to compare a failed Claude search call with a successful ChatGPT one using the audit log, timestamp, user and tool name. That should help isolate where authorization diverges.

Hardik Babbar

Atlassian Engineering team fixed this bug.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

connector

rovo-atlassian-intelligence

claude