Playwright MCP

Hosted Playwright MCP server for web testing

Meandr runs Microsoft's Playwright MCP server from the Docker MCP catalog. Your QA agent gets its own key, and a policy keeps the browser on your staging URLs.

Try for free Quick tour video

The setup

Set up a hosted Playwright MCP server for a QA agent on staging

  1. 01 Run

    Run Playwright from the catalog on a shared machine

    In Run a server, pick Playwright and give the hosted Playwright MCP server a share of the machine's memory.

    • Machine Shared 512 MB, Memory allocation 194 MB
    • Max processes 2, Idle timeout 60 seconds
    • Hosted servers have internet access, so the browser reaches your public staging site
    • Staging behind a VPN or IP allowlist: run Playwright on a machine in your network with the Meandr CLI, under the same policies and Traffic
    MCP Hosting: machines and versions

  2. 02 Tools

    Switch on the browser tools the tests need

    The Server catalog lists Playwright's tools, marking the ones that only read the page as read-only and the rest as destructive.

    • Upload files and Run Playwright code stay off, since the signup test doesn't need them
    • Tools you switch off never reach the agent
    AI Agent Security: only the tools an agent needs

  3. 03 Agent key

    Give the QA agent its own key

    Add an agent named qa-agent and a key for it, then use the workspace connection URL your Claude Code or Cursor already points at.

    • Only agents with a Meandr key can drive the hosted browser
    • Rotate or revoke it on the Keys page; other agents keep working
    AI Agent Security: one key per agent

  4. 04 URL policy

    Keep the browser on staging and allow the other browser actions

    Add three policies on the Playwright server, in this order.

    • #1 staging only: Allow opening pages and new tabs whose address starts with https://staging.acme.com/
    • #2 off staging: Deny opening any other site in a page or a new tab, with a reason code
    • #3 browser tools: Allow the rest, so page reads, form filling, waits and tabs work
    MCP Governance: request conditions

  5. 05 Test

    Test the signup page and read the run in Traffic

    Prompt: “Test signup on staging.acme.com/signup with a new user and screenshot the result.”

    • The agent opens the signup page and reads it to find the fields
    • Playwright fills the form, clicks Sign up and takes a screenshot
    • Result: the welcome page loads and the screenshot returns to the agent
    • The agent tried to open the Terms page on www.acme.com, the off staging policy denied it, and the agent got an error instead of the page
    AI Governance: the audit record

Questions about hosted Playwright

Do I need to deploy anything?
No: pick Playwright in Run a server and choose a machine, and Meandr runs it with no Dockerfile to write and no port to open.
Where do the screenshots go?
Playwright returns the screenshots to the agent in the tool response, since files on a hosted machine's disk last only until the machine is replaced.
Can two testers use one hosted Playwright?
Yes: each agent that connects gets its own process, up to the Max processes you set.
Can the agent open a site outside staging?
The staging only policy covers opening a page or a new tab, but clicking an external link or running a script can still leave staging, so switch off Evaluate JavaScript and Run Playwright code in the server catalog if your tests don't need them.
Which clients can drive the browser?
Any MCP client that connects to Meandr, including Claude Code, Codex, Cursor and VS Code.

Run Playwright for your QA agent

Pick Playwright from the catalog, allow your staging URLs, and connect from the client you already use.

Try for free

Questions? Email us