Assistant cannot complete connector OAuth/connect flow from within a session — must direct user to Settings UI
Description
When a user asks Claude Code to connect a new MCP connector (e.g. Readwise) on their behalf, the assistant cannot complete the connection itself. The mcp-registry tools available (search_mcp_registry, suggest_connectors) can at best search a catalog or render a "Connect" button/card for the user to click — the actual OAuth/authorization flow only happens in the app's Settings → Connectors UI, outside any tool the assistant can invoke.
This means for any new-connector request, the assistant's only path is to tell the user to go do it manually in Settings, even when the assistant has broad tool access (Bash, gh CLI, etc.) for other tasks. There's no in-session action or deep link the assistant can trigger to initiate or complete a connector authorization.
Expected behavior
Either:
- The assistant should have a tool that can initiate a connector's OAuth flow directly (e.g. return an authorization URL the user can click without leaving the conversation), or
suggest_connectorsshould reliably render an actionable "Connect" affordance inline (in this session it did not clearly do so — see related issue #75958 wherelist_connectors/search_mcp_registryreturned empty), so the user isn't forced to separately navigate to Settings.
Actual behavior
The assistant can only tell the user "go to Settings → Connectors and connect it yourself" — there is no tool-mediated way to complete or even surface the connection flow from within the chat session.
Repro steps
- Ask Claude Code to connect a new service (e.g. "connect Readwise").
- Observe the assistant has no tool that completes the authorization — it can only search a registry (which itself is broken per #75958) or tell the user to use the Settings UI.
Environment
- Surface: Claude Code, session with
mcp-registrytools (list_connectors,search_mcp_registry,suggest_connectors) available. - Related: #75958 (registry tools return empty), #75959 (assistant capability self-reporting inconsistency).
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗