Free tools Windows power users keep installed
One-click scans. No signup required.
Playwright MCP lets an MCP client control a browser through Playwright. The official documentation describes interactions based on structured accessibility snapshots, rather than pixel-based operation. To install the server, use Node.js 20 or newer and an MCP client; the standard command runs @playwright/mcp@latest with npx. The browser downloads automatically the first time it is used. Read the official Playwright MCP guide for current options and client-specific setup.
What Playwright MCP does
Playwright MCP exposes browser automation through the Model Context Protocol (MCP), allowing a compatible client to request browser actions. The official guide describes the server as enabling interaction with web pages through structured accessibility snapshots. This is distinct from an approach that operates only by interpreting pixels on screen.
Documented examples include navigating to a page, clicking controls, filling fields, taking screenshots, mocking APIs, and running Playwright code. These are examples of capabilities in the official guide, not a guarantee that every site or action will work in every environment. The MCP client sends requests to the server; the server uses Playwright to carry them out in a browser.
The server is software, not a physical product. A compatible computer, Node.js runtime, MCP client, and browser environment are the relevant setup components. You can let the server download a browser or choose a documented way to connect to an existing one.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Install the server
Prerequisites
- Node.js 20 or newer. Confirm the installed version with
node --version. - An MCP client. Follow that client’s current instructions for registering an MCP server; configuration paths and formats are client-specific.
- A browser option. The standard setup downloads its browser automatically on first use. Existing-browser connection options are covered below.
Standard npx command
The official example invokes the latest published package with npx:
npx @playwright/mcp@latest
Configure your MCP client to launch that command as its Playwright MCP server. The exact JSON or UI fields depend on the client, so do not copy a configuration block from another client without checking its current documentation. The package selector @latest means the version resolved by npm when the command runs; for a controlled deployment, check the package’s current versioning guidance and your client’s supported configuration.
On first use, the browser download is automatic according to the official installation page. Allow the download and any required network access in the environment where the server runs. A managed or restricted environment may require an administrator to permit package and browser downloads.
Choose how the browser and session are managed
Decide whether the server should launch and manage a browser, retain a profile between runs, start with a clean context, or connect to a browser you already use. The right choice depends on whether a task needs existing authentication and whether session state should persist.
Recommended Free Tools
| Mode | Browser and session behavior | Useful when |
|---|---|---|
| Isolated context | Starts a fresh session rather than reusing prior cookies and login state. | You want a clean run that does not depend on a previous sign-in. |
| Persistent profile | Retains browser profile data, including login state and cookies. | Repeated work should reuse a profile. Treat retained authentication as sensitive state. |
| Shared browser context | Shares context state as configured by the server. | Multiple interactions need to use the same configured context; check the current guide for its behavior and implications. |
| Existing browser connection | Connects to a running or installed browser by a documented connection method. | You need an existing browser session, browser channel, or extension-dependent page. |
Persistent state is convenient, but it also means later tasks may inherit cookies and authentication. Use an isolated context when a clean session is important. Do not put a profile containing sensitive account access somewhere that an unintended user or process can read.
Headed, headless, and browser selection
The official getting-started guide documents headed mode as the default. In headed mode, the browser window is visible. Add --headless to switch to headless operation when a visible window is not needed or the environment does not provide a display.
The guide lists these browser choices: chrome, firefox, webkit, and msedge. Check the current guide for the exact browser-selection flag and any browser-specific requirements before adding it to the launch command; do not assume option spelling across versions. Browser behavior and availability can differ by operating environment.
Headed mode is useful when you need to observe the browser while diagnosing a task. Headless mode suits noninteractive environments, such as a server or CI runner, if the chosen environment supports the necessary browser runtime. Neither mode changes the importance of choosing the right profile and session policy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Connect Playwright MCP to an existing browser
The official connection guide describes several approaches: named Chrome or Edge channels, a Chromium CDP endpoint, a Playwright endpoint, and the browser extension. They differ in how the server finds or attaches to the browser, so use the matching section of the current browser connection guide for configuration details.
Browser channels
A named Chrome or Edge channel lets the server use the corresponding browser channel instead of relying only on its automatically downloaded browser. This can be appropriate when the installed browser is the environment you need to automate. Availability depends on the host machine and the browser installation.
CDP or Playwright endpoint
The guide also supports connecting through a Chromium Chrome DevTools Protocol (CDP) endpoint or a Playwright server endpoint. These methods require a reachable endpoint and matching connection configuration. Keep endpoint access restricted to trusted clients: a browser connection can expose the pages and session state available to that browser.
Browser extension
Extension mode reuses existing tabs, sessions, cookies, and installed extensions. The official guide identifies SSO or two-factor authentication, extension-dependent pages, and already-open tabs as reasons to consider it. Because it operates through an existing browser context, the same access-control concern applies: the connected session may include sensitive pages and logged-in accounts. The guide does not promise that extension mode will work with every site or authentication flow.
Configure transport and advanced options
For ordinary use, configure the server in the MCP client you use. Client setup is not universal; follow the client’s current MCP-server instructions rather than assuming one configuration path works everywhere.
The Playwright guide also documents an advanced JSON configuration file and standalone HTTP transport. Its HTTP example uses port 8931 and an MCP URL ending in /mcp. Treat those as example implementation settings, not universal values: verify the current guide for the required flags, URL, and security setup before exposing or connecting to a server. The guide notes a five-second heartbeat timeout and the PLAYWRIGHT_MCP_PING_TIMEOUT_MS setting; check the current documentation before changing timeout behavior.
Additional configuration described by the guide includes browser choice and context behavior. Prefer the official configuration reference for exact option names and accepted values, which can change between package releases.
Use the server from an MCP client
- Install or select an MCP client and confirm it supports launching or connecting to an MCP server.
- Register the standard command,
npx @playwright/mcp@latest, using the client’s documented server configuration format. - Choose a session approach: fresh isolated context, persistent profile, shared context, or an existing-browser connection.
- Start the client and allow the browser download if using the managed-browser route.
- Ask the client to perform a small, low-risk browser task, such as navigating to a public demonstration page and reading or clicking a visible control.
The official getting-started guide uses TodoMVC as a demonstration and shows interactions through browser tools. A client’s available tool presentation and prompt flow may vary. Begin with a public page before granting access to an authenticated account or sensitive application.
Troubleshooting common setup problems
The command fails or npx cannot start the package
Check node --version and confirm Node.js is version 20 or newer. Verify that the MCP client launches the command and package argument exactly as intended, and that its runtime environment can resolve npx and reach the package registry. If you use a restricted network, browser and package downloads may need to be allowed by the environment administrator.
The browser does not appear
The standard guide describes headed mode as the default, while --headless requests no visible browser window. Check whether the launch configuration includes --headless and whether the host has a display available. In a server environment without a display, headless operation may be the appropriate choice.
The server cannot connect to the intended browser
Confirm the selected connection method matches the target: browser channel, CDP endpoint, Playwright endpoint, or extension. Check the current connection guide for the required option names and ensure the endpoint is reachable from the server process. A browser that is not installed, running, or accessible cannot be attached to merely by selecting its name.
The task is not signed in
An isolated context starts fresh and will not automatically inherit another browser’s cookies. Choose a persistent profile if retaining its login state is appropriate, or use an existing-browser connection such as extension mode when the task specifically needs a current authenticated session. Do not assume that every SSO or 2FA flow is automatable; the extension is an option, not a site-specific success guarantee.
HTTP transport does not respond as expected
For standalone HTTP mode, compare the listening port and MCP endpoint with the values used by your client; the guide’s example uses port 8931 and a path ending in /mcp. If heartbeat checks time out, consult the current guide for the five-second behavior and the PLAYWRIGHT_MCP_PING_TIMEOUT_MS setting. Avoid opening an HTTP endpoint to untrusted networks.
Reliability, performance, and safe operation
Browser automation depends on more than the MCP server starting successfully: the browser must launch or be reachable, the page must load, and the requested interaction must match the page’s actual accessible structure. Use a short, observable first task to distinguish a client configuration problem from a browser or site-specific issue.
- Keep state intentional: isolated sessions reduce dependence on earlier runs; persistent and shared contexts can improve continuity but carry cookies and login state forward.
- Match the environment: use headed mode when visibility aids diagnosis and headless mode for a suitable non-display environment.
- Control access: an existing authenticated browser may expose logged-in accounts, open tabs, and extensions. Restrict who can connect to it or to an HTTP endpoint.
- Pin and review changes when stability matters: the documented quick start uses
@latest, which resolves the latest package at launch time. Check current package and client documentation when updating a production workflow.
Or skip the browser setup
If your goal is a screenshot rather than interactive browser automation, ScreenshotNeo is a separate website screenshot API and MCP server for developers. A single GET request can return a PNG, JPEG, WebP, or PDF. For example, this cURL request captures a page as WebP:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo API documentation for request options. Cookie banners are accepted before capture and more than 60 known consent platforms, newsletter popups, and chat widgets are removed; each cleanup step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, with response headers reporting the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.
The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Frequently Asked Questions
Does Playwright MCP require a particular computer or physical device?
No particular physical product is central to the documented setup. It is software-based and uses a compatible runtime, MCP client, and browser environment.
Can Playwright MCP take screenshots as well as interact with pages?
Yes. Taking screenshots is among the browser actions listed in the official getting-started guide.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Does connecting the browser extension guarantee access to every SSO-protected site?
No. The guide identifies SSO and 2FA as reasons to consider extension mode, but does not promise success for every site or authentication flow.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
