Use browser automation with Claude Desktop

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

1. Connect Claude Desktop

Open Settings, then Developer, then Edit Config, and add this to claude_desktop_config.json. Restart Claude Desktop. Claude Desktop's config file runs local commands, so the remote server is reached through the mcp-remote bridge (needs Node.js).

{
  "mcpServers": {
    "wingman": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "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 Claude Desktop 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 Claude Desktop