Failing to add docs as project knowledge in Claude using the Rovo Connector

[Oren Koren]

Hello,

We have recently connected Atlassian Rovo connector to our Claude accounts, but we can't seem to be able to add any docs or other resources to any project, the only options available from the resource dropdown are "confluence-widget-openai" and "jira-widget-openai"
Any URL we try to paste in the resource bar fails with 400 - Bad Request

{
    "type": "error",
    "error": {
        "type": "invalid_request_error",
        "message": "Failed to fetch resource"
    },
    "request_id": "some_request_id"
}

The free text search does not work either, see screenshot:

[Dr Valeri Colon _Connect Centric_]

@Oren Koren Welcome to the community! This does not appear to be isolated. Another thread reports the same Claude + Rovo connector behavior: only confluence-widget-openai / jira-widget-openai appear, URL fetches fail, and search does not resolve resources. Since Claude’s Atlassian connector is meant to access Jira and Confluence content, this likely needs Atlassian/Anthropic support to check the connector resource resolution path.

[Tomislav Tobijas]

Hi @Oren Koren ,

I'm going to move this question to Rovo Q&A forum section. As I haven't worked with Claude that much, I cannot give any actual insights. 

You could maybe try one of the following:

• Do a re-authentication (re-connection)
• Which Claude plan do you have? I do think it works best with Claude Team or Enterprise but still might work okay on other plans as well.
• What I also found is that... "Enable Tools: In Claude, open the Search & Tools menu and ensure that the specific tools for Jira and Confluence are toggled on..."
  You'll need to try that one out 👀
• Also, are you using Claude desktop or the web-based interface?

Cheers,
Tobi

[Oren Koren]

Hi @Tomislav Tobijas 
Thanks,

I tried all of the above, it didn't help, issue persists in both web-based and dekstop interfaces.

We have a Claude Enterprise account.

Thanks

Oren

[Tomislav Tobijas]

Alright. In that case, I'd probably suggest reaching out to Atlassian Support - they can check backend information and maybe point you in the right direction on what to try out to fix this.