Third-party Atlassian MCP connectors broken after atlassian-python-api 5.0.0 - Confluence Cloud tools crash with AttributeError

### What happened?

All third-party Atlassian MCP connectors in Claude.ai (based on sooperset/mcp-atlassian) stopped working for Confluence Cloud operations on or after August 15, 2026.

Every core Confluence tool crashes with AttributeError:
confluence_get_page > 'Cloud' object has no attribute 'get_page_by_id'
confluence_create_page > 'Cloud' object has no attribute 'create_page'
confluence_update_page > 'Cloud' object has no attribute 'update_page'

Tested across 3 independent connector instances connected to different Atlassian Cloud sites - all fail identically.

Root cause is known (identified in [sooperset/mcp-atlassian#1585](https://github.com/sooperset/mcp-atlassian/issues/1585)): mcp-atlassian 0.23.0 declares atlassian-python-api>=4.0.0 with no upper bound. On August 15, atlassian-python-api 5.0.0 was released, which rewrites atlassian.Confluence into a dispatcher that delegates to a Cloud class missing most legacy methods. Any environment that resolved dependencies on or after August 15 gets the broken 5.x version.

The fix is already merged on mcp-atlassian main ([#1589](https://github.com/sooperset/mcp-atlassian/pull/1589) - pins atlassian-python-api>=4.0.0,<5.0.0), but no patch release (0.23.1) has been published to PyPI yet.

The issue for Claude.ai specifically: for local installs, users can pin the transitive dependency as a workaround (uvx --with 'atlassian-python-api==4.0.7'). For Claude.ai remote connectors, dependency resolution happens server-side and users have no way to pin anything. These connectors will remain broken until either:
1. sooperset/mcp-atlassian publishes a patch release to PyPI with the cap, and
2. Claude.ai re-resolves/rebuilds the remote connector against the fixed version

### What did you expect to happen?

Confluence tools should execute successfully, as they did before August 15.

### Steps to reproduce

1. Open any conversation in Claude.ai with a third-party Atlassian MCP connector connected to a Confluence Cloud site
2. Use tool_search to find confluence_get_page - it loads successfully
3. Call confluence_get_page with any valid page ID
4. Observe: 'Cloud' object has no attribute 'get_page_by_id'

### Area

MCP Connector (adding/managing servers)

### MCP Server (if applicable)

sooperset/mcp-atlassian — https://github.com/sooperset/mcp-atlassian Deployed version: 0.23.0 with atlassian-python-api 5.0.x (resolved after August 15, 2026). Upstream issue: https://github.com/sooperset/mcp-atlassian/issues/1585 Upstream fix (merged, not released): https://github.com/sooperset/mcp-atlassian/pull/1589

### Error messages or logs

```shell
confluence_get_page:
"Failed to retrieve page by ID '': Error retrieving page content:
'Cloud' object has no attribute 'get_page_by_id'"

confluence_create_page:
"'Cloud' object has no attribute 'create_page'"

confluence_update_page:
"'Cloud' object has no attribute 'update_page'"

confluence_search:
"404 Client Error: Not Found"
(or returns Confluence SPA index.html instead of JSON)
```

### Additional context

Requested action: rebuild/re-resolve the remote mcp-atlassian connector once the upstream patch release (0.23.1+) ships to PyPI, so the dependency resolves to atlassian-python-api 4.0.7 instead of 5.0.x.

Broader concern: this class of breakage (unbounded transitive dependency publishes a major version with breaking API changes) is likely to recur with other third-party MCP servers. A dependency pinning or version-lock mechanism for remote connectors - or periodic re-validation of advertised tools against actual runtime - would prevent silent breakage.

Related feature request: multi-site authorization for the first-party Atlassian connector (Rovo). Currently it only binds to one cloudId, forcing users who work across multiple Atlassian Cloud sites to rely on third-party MCP servers. Native multi-site support would reduce exposure to third-party dependency issues like this one.

Old issue: https://github.com/anthropics/claude-ai-mcp/issues/866