GHL (LeadConnector) MCP connector requires re-authentication every new CLI session

The claude.ai GoHighLevel connector (LeadConnector MCP endpoint, https://services.leadconnectorhq.com/mcp/anthropic/v2) requires re-authentication via /mcp at the start of nearly every new Claude Code CLI session, even though claude mcp list reports the connector as "✔ Connected."

Observed 2026-07-23: within a session, once authenticated, the connector's tools work fine — the issue is specifically tied to starting a new CLI session, not to a time-based token expiry within a session. This suggests the OAuth access/refresh token for this connector isn't being persisted to disk (or isn't being reloaded) between CLI launches, since claude mcp list's "Connected" status reflects transport reachability, not auth validity.

Confirmed CLI-specific: the same GoHighLevel connector/account does not require repeated re-auth when used outside the CLI (e.g. via claude.ai web), which points to this being a Claude Code CLI token-persistence bug rather than a LeadConnector-side short token TTL.

Ruled out: this is not the ANTHROPIC_API_KEY-precedence issue described in earlier claude.ai-connector docs — no ANTHROPIC_API_KEY is set in this environment's shell profiles.