No way to connect/authorize a connector (e.g. Readwise) directly from within a Claude Code session #75955

Description

When a connector (e.g. Readwise) is not yet connected, there is no way to initiate or complete the connect/auth flow from within the Claude Code session itself. The user has to leave the conversation, go to the separate Connectors panel UI, and click "Connect" there — Claude cannot trigger, complete, or verify that flow on the user's behalf.

Steps to reproduce

1. Ask Claude in a session whether a given connector (e.g. Readwise) is connected.
2. Claude can check list_connectors / the session's tool list, but has no tool to initiate an OAuth/connect flow for a connector that isn't yet connected.
3. The only path is for the user to manually open the Connectors panel and click "Connect" outside the conversation.

Expected behavior

Ideally Claude could either (a) surface a direct in-conversation link/action to start the connect flow for a specific connector, or (b) at minimum have a reliable tool to confirm once the user has completed it, so troubleshooting doesn't require manual round-tripping between the chat and a separate settings panel.

Actual behavior

• No tool exists to initiate a connector's auth flow from the session.
• Combined with the issue in Readwise connector: UI shows 'Connect' despite being reported as already connected #75954 (Connectors panel not reflecting true connection state), this makes it very hard to diagnose or fix a stuck/mismatched connector without leaving the conversation and guessing at UI state.

Additional context

Related to #75954.