VS Code extension only exposes tools from locally-configured MCP servers, not claude.ai account connectors

Description

In the Claude Code VS Code native extension, only MCP servers defined in local
config (~/.claude.json mcpServers) have their tools registered in the
session's tool list. MCP servers connected via claude.ai account connectors
(Settings -> Connectors) show as healthy/authenticated but their tools never
appear as available/deferred tools in the extension.

Environment

• Claude Code version: 2.1.168
• Surface: VS Code native extension (Windows 11)
• claude mcp list (run from integrated terminal) shows 4 servers connected:

Slack, Figma, Atlassian (claude.ai connectors) + github (local mcpServers
config, HTTP transport with bearer token)

Steps to reproduce

1. Connect one or more MCP servers via claude.ai -> Settings -> Connectors

(e.g. Slack, Figma, Atlassian), while also having a locally-configured
MCP server in ~/.claude.json (e.g. github).

1. Open the repo in VS Code with the Claude Code extension.
2. Ask Claude to search available/deferred tools, or attempt to use a

connector's tool.

Expected
All connected/authenticated servers' tools are available in the session,
matching what claude mcp list reports.

Actual
Only the locally-configured server's (github) tools are available. The
claude.ai connector tools (Slack, Figma, Atlassian) are absent from the tool
list despite claude mcp list reporting them as "Connected".

Additional context

• Confirmed this is extension-specific: running claude from a plain

terminal (not the VS Code extension) in the same repo correctly exposes
all 4 servers' tools.

• Reloading the VS Code window does not resolve it.
• Toggling the connector off and back on (claude.ai -> Settings -> Connectors)

does not resolve it.

• ~/.claude/settings.json permission history shows tools like

mcp__claude_ai_Atlassian__getJiraIssue and
mcp__claude_ai_Figma__get_design_context were previously used
successfully, so this is a regression rather than a config gap.