On 19 November 2026, an independent maintainer released playwright-mcp-server-hellork 0.2.1 on PyPI to provide Playwright browser automation over the Model Context Protocol in Python. According to the PyPI page, the maintainer built the server because Microsoft's Node.js implementation had no Fedora package at the time and could not be fixed to work with the crush agent. The package acts as an MCP connector to Playwright rather than a standalone browser, and the listing states it is not affiliated with or endorsed by Microsoft.1

What inputs and outputs does the workflow handle?

An MCP client passes URLs, element selectors, input text, or JavaScript snippets to tools such as navigate, click, type, and evaluate, according to the PyPI documentation. During a multi-page session, the server can open new tabs with new_page, switch between pages, and wait for selectors before reading content. It returns page titles, URLs, element text, or full HTML content, and it exposes full-page or element screenshots as base64 PNG images through MCP resource URIs such as screenshot://{page_id}.1

How do builders install and run it?

Builders install the package with pip install playwright-mcp-server-hellork or from the GitHub repository using pip install -e ., then install a browser binary with playwright install chromium, the PyPI listing states. Running playwright-mcp launches headless Chromium by default with a 30000.0 ms default timeout. Users can pass flags such as --headed or --browser firefox, or embed the server in Python applications by importing create_server, ServerConfig, and BrowserConfig and calling await server.run_stdio().1

What are the limits and risks?

The PyPI comparison table notes that this server uses the direct Playwright API and supports only stdio transport, whereas Microsoft's official server uses accessibility snapshots and supports both stdio and SSE. The maintainer reports that the codebase was mostly created with the crush agent using NVIDIA Nemotron 3 Ultra without consulting Microsoft's TypeScript source. PyPI also indicates that the 0.2.1 release files carry no provenance metadata, and the maintainer advises users to run the package at their own risk. It runs on Playwright for Python, whose driver launches its own bundled Node.js unless one is configured, so the server removes the need for a separate Node.js install and for Microsoft's Node-based server, not for Node.js itself.12