Skip to content
SUPERVISED BROWSER INTEGRATION · CLIENT Name withheld

Playwright MCP + Cline

Human-approved browser actions through Cline on Windows, with restart, recovery and saved evidence.

Illustration of Playwright MCP + Cline: a Cline browser action waiting for human approval beside a test page
ILLUSTRATION
CURRENT SCOPE

Local Windows rehearsal verified · client acceptance pending

WHO IT'S FOR

Client project · Name withheld

Anonymous client-requested Windows integration. Verified preparation used the owner’s computer and test tasks; client-machine installation, funded work and contractual acceptance remain pending.

THE ENGINEERING

Prepared a Windows integration extending an existing Cline installation with Microsoft’s official Playwright MCP server. Two recorded local Cline GUI workflows each passed five browser test assertions. Actual editor restarts, server disable/re-enable and exact configuration restoration were exercised. An explicit process working directory fixed misplaced screenshot evidence; the final browser run saved the verified image in its intended workspace. Existing provider settings, unrelated MCP servers and browser profiles were preserved, with automatic approvals disabled. Client-machine installation, live walkthrough and contractual acceptance remain pending.

PlaywrightMCPClineWindowsNode.js

BEFORE → AFTER

Real problems from this build, what I changed and the verified result.

  1. CASE 01
    Before

    A connection indicator does not establish that Cline can execute a complete browser workflow.

    After

    The current project overview records two local GUI runs with five browser assertions passing in each; client-operated verification remains pending.

    How I fixed it

    Ran the test task through Cline’s Windows GUI with individual action approvals and repeated it after real editor restarts.

  2. CASE 02
    Before

    A screenshot’s relative path inherited the editor application directory instead of the intended workspace.

    After

    The final screenshot was verified as a real file in the intended workspace and visually inspected; exact restoration and disable/re-enable were also exercised.

    How I fixed it

    Added an explicit MCP process working directory, restarted the editor and reran the full browser workflow.

Evidence reviewed: Current technical overview and owning local evidence reviewed October 18, 2026; client acceptance pending