Request: Support for MCP Server Configuration in VS Code extension (Claude Code)

[Leuconoe]

Currently, there is no built-in interface or automatic detection for adding custom MCP servers within the VS Code extension (Claude Code). While MCP servers can be configured for the Claude Code CLI, the VS Code extension lacks a corresponding Client Configuration to recognize and connect to servers like UnityMCP.
Status & Workaround
I attempted to use UnityMCP within VS Code, but it was not detected. The only way to resolve this was to manually inject the server configuration into the VS Code User Settings (settings.json):

"claudeCode.mcpServers": {
  "UnityMCP": {
    "type": "http",
    "url": "http://127.0.0"
  }
}

Suggested Improvements

• Setup Guide: It would be helpful to provide specific instructions on how to bridge the configuration between the CLI and the VS Code extension so that users don't have to define the server in two different places.

[Scriptwonder]

I think the non-terminal VS Code CC extension always has some issues with detecting the MCP server. My personal usage is Terminal CC with the VS Code extension and I would suggest you try that. I tried checking before but could not find the real issue that make these two versions distinct (maybe the non-terminal version of CC extension lacks some further support? It also does not support 1M context, which further impact typical MCP usage)