W

Weboperator

MCP server · by KazKozDev

Browser Automation npm v1.5.1

Hands your live Chrome tab to any MCP client — snapshot, navigate, click, type, extract.

View source ↗ More servers

Install

Run one of the commands below, then add the client config underneath.

npmnpx -y weboperator-mcp

Client configuration

Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.

mcpServers{
  "mcpServers": {
    "weboperator": {
      "command": "npx",
      "args": [
        "-y",
        "weboperator-mcp"
      ]
    }
  }
}

About this server

Weboperator is listed in the Browser Automation category of the MCPNav directory. It is distributed as npm and can be loaded by any client that speaks the Model Context Protocol.

Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.

Frequently asked questions

What is the Weboperator MCP server?

Weboperator is an MCP server by KazKozDev. Hands your live Chrome tab to any MCP client — snapshot, navigate, click, type, extract.

How do I install Weboperator?

Install it with: npx -y weboperator-mcp. Then add the JSON config to your client's MCP settings and restart the client.

Is Weboperator free to use?

The MCP server itself is free to install. The source is public on https://github.com/KazKozDev/WebOperator. Any third-party API it calls (such as a search or maps API) may require its own key and billing.

Which clients support Weboperator?

Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.