[BUG] VS Code extension: claude.ai MCP connectors connected in CLI but not injected into extension sessions

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

claude.ai MCP connectors (Zoho CRM, Gmail) show as connected in claude mcp list but /mcp in the VS Code extension chat shows no servers connected, and tool schemas aren't injected into VS Code extension sessions. Works correctly in terminal CLI. Request: full MCP parity between terminal and VS Code extension.

What Should Happen?

MCP connectors authenticated via claude.ai (Zoho CRM, Gmail) should be fully available in VS Code extension sessions — both visible via /mcp and callable as tools — matching the behavior of the terminal CLI.

Error Messages/Logs

Steps to Reproduce

1. Connect claude.ai MCP connectors (Zoho CRM, Gmail) via claude.ai Settings → Integrations
2. Open Claude Code in VS Code extension
3. Run claude mcp list in terminal — servers show as connected
4. Type /mcp in the VS Code extension chat — shows no servers connected
5. Attempt to use Zoho CRM or Gmail tools in VS Code extension session — tools are not available
6. Run same workflow in terminal CLI (claude in Mac terminal) — tools work correctly

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_