Desktop MCP toggle can fail or block on resource catalog refresh

Description

After a successful MCP toggle connect, the Desktop UI synchronously refetches the global MCP resource catalog across all connected servers. A slow or unsupported resources/list call therefore blocks the toggle or surfaces a false failure. The impact rises with more connected MCP servers, but one problematic server is sufficient.

Expected behavior

The MCP toggle should complete after the MCP connection status is refreshed. Resource catalog discovery should run independently and best-effort; a slow, unsupported, or rejected resources/list must not block or fail the toggle.

Steps to reproduce

1. Configure at least one MCP server whose resources/list response is slow or unsupported.
2. Open the Desktop app and enable that MCP server.
3. Observe that the toggle waits for resource discovery or reports a failure despite the connection succeeding.

Validation

The cause was reproduced and validated locally with a focused unit-test scenario in which resource discovery remains pending after connect: the toggle resolves without waiting for it. A rejection case also verifies that the background resource refresh is safely handled without an unhandled rejection or toggle failure.

Additional context

This is a Desktop MCP toggle flow issue; no credentials, private endpoints, or local paths are required to reproduce the behavior.