pickfit

BrowseMCP servers

Plasmate

Browser engine that compiles HTML into structured Semantic Object Model JSON for agents.

Use it

Before you install: known vulnerabilities

pickfit found 5 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:wasmtime 36.0.13 Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation (GHSA-897f-g5gm-fmxm, critical, fixed in 36.0.19)
  • crates:quinn-proto 0.11.15 Peer minimum ACK delay can panic quinn-proto when ACK_FREQUENCY transmission is enabled (RUSTSEC-2026-0340, high, fixed in 0.11.18)
See 3 more

Linux x86_64

You need first

  • Runtimes: Rust 1.88+
  • Needs the network
  1. download install script to /tmp/plasmate-install.sh

    curl -fsSL https://plasmate.app/install.sh -o /tmp/plasmate-install.sh
  2. install plasmate v0.5.1 with PLASMATE_VERSION=v0.5.1 sh /tmp/plasmate-install.sh

    PLASMATE_VERSION=v0.5.1 sh /tmp/plasmate-install.sh
Where the README and reality differ
  • README: curl -fsSL https://plasmate.app/install.sh | sh installs latest
    What worked: install.sh defaults to TAG v0.1.1; must set PLASMATE_VERSION=v0.5.1 to get latest release (v0.5.1 assets)
  • README: plasmate compile takes file as positional arg
    What worked: plasmate compile requires --file <FILE> flag; positional /tmp/sample.html errors

Check that it works

plasmate serve --protocol cdp --host 127.0.0.1 --port 9222

The output should contain “CDP server listening on 127.0.0.1:9222”.

First thing to try

plasmate serve --protocol cdp --host 127.0.0.1 --port 9222

Add it to your agent

claude mcp add plasmate -e PLASMATE_MCP_HTTP_TOKEN='<PLASMATE_MCP_HTTP_TOKEN>' -- plasmate mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "plasmate": {
      "command": "plasmate",
      "args": [
        "mcp"
      ],
      "env": {
        "PLASMATE_MCP_HTTP_TOKEN": "<PLASMATE_MCP_HTTP_TOKEN>"
      }
    }
  }
}

You fill in

  • PLASMATE_MCP_HTTP_TOKEN: capability token for HTTP transport (required)

Ask the user for PLASMATE_MCP_HTTP_TOKEN; pickfit never had a value, so these are placeholders.

Run plasmate mcp to start the MCP server, then connect your MCP client to it.

What it does

  • Use the browser through MCP tools
    How to use it
    1. Start the server with plasmate mcp and connect your MCP client to it.
    2. Call the fetch_page tool with a url argument such as <url> to get the page content.
    Tested
  • Compile HTML into a Semantic Object Model
    Not tested
  • Fetch pages as structured SOM JSON
    Not tested
  • Serve a CDP endpoint that works with Puppeteer
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 1 of 4 features work
  4. Works offline

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • fetch a page and get structured SOM JSON
  • serve a Puppeteer-compatible CDP endpoint
  • serve the native AWP agent protocol
  • extract clean readable text from a page
  • capture a page screenshot

An alternative to Lightpanda and Chrome.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 0.5.1

An MCP client handshake over stdio listed 14 tools, and a call to fetch_page returned a result.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.