Vew Mcp

io.github.YawLabsPublished by GitHub account YawLabsv0.4.3Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyBrowser Automation

Server details

Identifier: io.github.YawLabs/vew-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account YawLabs for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.YawLabs%2Fvew-mcp.svg)](https://sourceweft.com/mcp/io.github.YawLabs%2Fvew-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant drive a real Chromium browser through Playwright, using compact, ref-addressable page snapshots.

What you can do: Control a real Chromium browser via Playwright from the assistant session. Read compact page snapshots in which elements carry references the assistant can address. Act on page elements by those references rather than by raw markup.
When to use it: Useful when an assistant needs to operate a real browser on the user's machine, such as navigating pages and interacting with elements identified from snapshots, rather than only reading static content.
Requirements: Runs as a local process over stdio, installed from the npm package @yawlabs/vew-mcp, so Node.js and npm are needed. It is desktop-only and not web-executable. No authentication, environment variables or headers are declared. A Chromium browser driven by Playwright is required.

Before you install

The server drives a real browser on the user's machine, so actions taken in that browser can affect logged-in sessions and live sites. No credentials are declared, but the browser may carry existing session state. Review what the assistant is allowed to do before connecting it.

Installation

In SourceWeft

Open Vew Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.4.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.