mcpField
V

vew-mcp

Local
@YawLabsBrowser Automation

About vew-mcp

Browser MCP: drive a real Chromium via Playwright with compact ref-addressable page snapshots

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "yawlabs-vew": {
      "command": "npx",
      "args": [
        "-y",
        "@yawlabs/vew-mcp"
      ]
    }
  }
}
Run commandnpx -y @yawlabs/vew-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@yawlabs/vew-mcp0.4.3

Tools

16

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
urlstringYesAbsolute http(s) URL to navigate to.
timeout_msintegerNoNavigation timeout in ms (default 30000).
wait_untilenumNoWhen to consider navigation finished (default 'load'). Use 'networkidle' for SPA-heavy pages.load | domcontentloaded | networkidle | commit

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.