Ubersuggest MCP: OAuth token not forwarded — all API calls return "Not connected" despite connector showing active

Bug Report

Summary: The Ubersuggest MCP connector (https://ubersuggest-mcp.neilpatelapi.com/mcp) shows as active/connected in the Claude Code desktop app Connectors panel, but every single API call — including auth_status, location_suggest, and keyword_overview — returns "Not connected". The OAuth token is not being forwarded from the desktop app to the MCP server calls.

---

Environment

• App: Claude Code desktop (macOS)
• MCP server: https://ubersuggest-mcp.neilpatelapi.com/mcp (Ubersuggest / Neil Patel)
• OS: macOS (Darwin 25.3.0)

---

Steps to reproduce

1. Add Ubersuggest MCP connector in Claude Code desktop app settings
2. Complete the OAuth authorization flow in the browser — browser shows "Connected, taking you back to the desktop app"
3. Return to Claude Code — Ubersuggest shows as an active connector in Settings → Connectors
4. In a conversation, call any Ubersuggest tool (e.g. auth_status, location_suggest, keyword_overview)
5. Every call returns "Not connected"

---

What was tried

• Disconnecting and reconnecting the Ubersuggest connector multiple times
• Logging out and back in to Ubersuggest in the browser
• Fully quitting and relaunching the Claude Code desktop app
• Starting fresh conversations after each reconnect attempt
• Loading tool schemas fresh via ToolSearch before each call

None of these resolved the issue. The tools are visible and their schemas load correctly — the authentication token is simply not reaching the MCP server.

---

Evidence

The user confirmed via screenshots:

• The Ubersuggest OAuth authorization page showed claude.ai ✓ — Ubersuggest with 9 permissions granted
• The post-auth page showed "Connected — Taking you back to the desktop app"
• The Claude Code desktop Connectors panel showed Ubersuggest listed as an active connector
• Despite all of the above, every MCP tool call returns "Not connected"

Note: The same Ubersuggest MCP works correctly in Cursor (Codex) using the same MCP server URL and the same user account. The failure is specific to Claude Code desktop.

---

Impact

This blocks an entire category of professional SEO research workflows that depend on Ubersuggest for keyword volume, SERP analysis, and competitor data. Users cannot work around this without switching to a different tool entirely.

---

Expected behaviour

After completing OAuth authorization and the connector showing as active, all Ubersuggest MCP tool calls should succeed and return data from the API.

Actual behaviour

All calls return "Not connected" regardless of auth state.