VS Code extension: claude.ai MCP connectors require CLI session first

Description

When authenticating a claude.ai MCP connector (e.g., Atlassian), the VS Code extension does not pick up the connection until a CLI session is run first. New VS Code sessions report no MCP tools available even after successful authentication.

Steps to Reproduce

1. Go to claude.ai/settings/connectors and connect Atlassian (OAuth flow completes successfully)
2. claude mcp list shows claude.ai Atlassian as "Needs authentication"
3. Restart VS Code completely
4. Open a new Claude Code session in VS Code
5. Ask Claude to access Jira → fails, says no Jira tools available

Workaround

1. After authenticating on claude.ai/settings/connectors, open a terminal and run claude (CLI)
2. In the CLI session, use a Jira tool (this establishes the connection)
3. Now restart VS Code and open a new Claude Code session
4. Jira tools are now available in VS Code

Expected Behavior

After authenticating a claude.ai connector in the browser, the VS Code extension should be able to use the connector without requiring a CLI session first.

Environment

• OS: Windows 11 Pro 10.0.26200
• Claude Code VS Code Extension
• Connector: Atlassian (Jira)

🤖 Generated with Claude Code