Failing to add Confluence pages as project knowledge in Claude using Rovo Connector

Question

We have connected the Atlassian Rovo connector to our Claude account but cannot add any specific Confluence pages or other resources to a project.

Symptoms:
- The resource dropdown only shows "confluence-widget-openai" and "jira-widget-openai"
- All URLs fail with "Failed to resolve URL. Make sure the MCP server supports this URL"
- Free text search returns "No resources found" for any query
- Issue persists on both web and desktop interfaces

What we have tried:
- Re-authenticating the Rovo connector
- Approving all interactive tool permissions (Retrieve Confluence page, Search Confluence with CQL, etc.)
- Pasting clean Confluence URLs without query parameters
- Searching by page name

We are on a Claude Enterprise plan. This appears to be a backend integration issue between the Atlassian Rovo MCP server and Claude's project knowledge file linking UI, as none of the standard troubleshooting steps resolve it.

Has anyone encountered this and found a fix?

Dr Valeri Colon (Connect Centric) · Answer

Welcome to the community @Astrid Vreugdenhil. We’re seeing similar reports from other Claude Enterprise users. If the connector is authenticated but resource search only shows confluence-widget-openai and jira-widget-openai, while URLs and search return no results, the issue appears to be in the Claude–Rovo integration layer rather than your Confluence permissions or connector configuration. At this point, I’d recommend opening a support ticket with Atlassian so they can investigate the backend integration logs.

Brad Ball_od1hs2 · Answer

We have this exact same problem. See attached screenshot.

Any Search term or URL you past in the search box shows:

Tomislav Tobijas · Answer

Moving this to Rovo forum group ➡️ as I haven't properly tested Rovo connector for Claude...
Someone will probably chime in here.

Apart from that, "Failed to resolve URL" often occurs when pointing to an outdated or incorrect MCP endpoint.
Have you checked these: Setting up clients ? (not sure if it's actually relevant for the connector itself, but might be useful)

Also, it might be a good idea to try to re-register the connector.

As for auth scopes, is the app listed under Atlassian Administration > Connected apps (probably buried under Apps > Site > *select site)

One more thing to check - domain allowlist...

Again, hopefully someone who actually tested this connector can jump in.

Cheers,
Tobi