Connect VS Code

Generate the VS Code format

Run the setup wizard and choose 2 · VS Code servers JSON. The output uses a top-level servers object and type: stdio.

Choose where to save it

Run MCP: Open User Configuration from the command palette for personal configuration, or use .vscode/mcp.json in the current project. Merge the actual generated entry into the existing servers object:

{
  "servers": {
    "work-projects": {
      "type": "stdio",
      "command": "/absolute/path/to/mcpbridge",
      "args": ["connect", "--profile", "work", "--client", "ci_example"],
      "env": { "MCPHUB_HOME": "/Users/you/.mcphub" }
    }
  }
}

Replace example values and preserve other existing servers.

Start and check the server

Run MCP: List Servers from the command palette, choose your server, and start or restart it. Confirm trust when requested. Check the tool list; if it fails, inspect server output and run doctor for the corresponding entry.

SSH and Dev Containers

The execution environment depends on VS Code configuration scope and remote setup. The connector, MCPHUB_HOME, sign-in, and authorization must all belong to the environment that actually runs it. Do not copy a local configuration directly into a container. See Multiple services and environments.

Official reference

See the official VS Code MCP documentation for configuration locations and management.