[BUG] MCP server authorization prompt doesn't appear in VSCode integrated mode, only in terminal mode

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?

When adding a new MCP server via claude add mcp command, the authorization
prompt to allow the MCP server only appears in standalone terminal mode, but
NOT in VSCode integrated Claude Code.

Actual behavior:

• No prompt appears in VSCode integrated mode
• MCP server is silently not loaded
• No error message or indication that authorization is needed
• The only workaround is to open Claude Code in a standalone terminal, accept

the authorization there, then return to VSCode

Impact:
Users have no way to know they need to authorize the MCP server when using
VSCode integration. The MCP server simply doesn't appear in the available
tools without any explanation.

What Should Happen?

An authorization prompt should appear asking to allow the MCP server, similar
to what appears in terminal mode.

Error Messages/Logs

Steps to Reproduce

1. Add a new MCP server configuration to .mcp.json in workspace root
2. Open Claude Code integrated in VSCode
3. Reload the VSCode window with "Developer: Reload Window"

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.1 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

The authorization prompt works correctly in standalone terminal mode but is
missing in VSCode integrated mode. This creates a confusing UX where new MCP
servers appear to "not work" without any feedback to the user.

Workaround: Run Claude Code in a standalone terminal first to accept the
authorization, then the MCP server becomes available in VSCode integrated mode.