Use browser automation with VS Code

Drive a real headless browser session: open, navigate, read, click and fill. Connect VS Code to the WingMan MCP gateway once and these tools are available in every conversation.

1. Connect VS Code

Create .vscode/mcp.json in your workspace (or run MCP: Open User Configuration for all workspaces), then start the server from the Chat view's tools picker.

{
  "servers": {
    "wingman": {
      "type": "http",
      "url": "https://wingmanprotocol.com/mcp"
    }
  }
}

2. The tools you get

Names and descriptions come straight from the live tool registry.

• browse_openOpen a PERSISTENT browser session (cookies/login survive across calls) and get a browser_id to drive with browse_navigate/snapshot/click/ty…
• browse_navigateNavigate an open session to a URL (SSRF-guarded).
• browse_snapshotAgent-native ACT view of the current page: interactive elements with stable @eN refs (for click/type) + a heading outline + challenge state.
• browse_clickClick an element by its @eN ref from the last browse_snapshot.
• browse_fillFill many fields at once {ref: value}; optional submit_ref to click after.

These tools are in the default tool list, so they show up as soon as the server connects.

3. Ask for it

Give VS Code a task that needs it, for example “use browse_open from wingman”. The tool call goes to https://wingmanprotocol.com/mcp and the result comes back into the conversation.

Browser automation with other clients

More tool categories for VS Code