Claude Desktop managed connector OAuth client change and Sume

If an admin configured a managed Sume connector with its own OAuth client, Claude Desktop v2.110.0 (2026-09-15) no longer connects it without credentials just because the server accepts unauthenticated connections. For Sume that is not a behaviour change worth worrying about, since the hosted server requires OAuth or an API key.

The practical step is to make sure the client credentials in the managed entry are complete.

What the changelog says

Managed connectors configured with their own OAuth client previously could connect without credentials when the server accepted unauthenticated connections. That path is closed.

At a glance

What Sume expects

Sume's hosted MCP uses OAuth with mcp:read required and mcp:write opt-in, or an API key sent as a Bearer token or x-api-key header. There is no anonymous mode to fall back on.

If a managed connector fails after upgrade, check the client id and secret, then have the user sign in again and grant the scopes they need.

• Verify client credentials in the managed entry.
• Re-consent if mcp:write is needed.
• Use an API key for headless setups.

Limits and what is not verified

The changelog does not explain what happens when the OAuth client is valid but the user has not signed in, and I did not test a managed Sume connector. Sume's OAuth details come from its docs.