Playwright mcp does not work

Bug Reports
1

Describe the Bug

after update to 1.0, playwright mcp does not work by Cursor – MCP Directory.
The mcp shows red.

It works in 0.5 version

Steps to Reproduce

after update to 1.0, playwright mcp does not work by Cursor – MCP Directory.
The mcp shows red.

Screenshots / Screen Recordings

Screenshot 2025-06-14 at 8.38.10 PM.png
Screenshot 2025-06-14 at 8.38.10 PM.png1084×147 6.56 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.2 (Universal)
VSCode Version: 1.96.2
Commit: 87ea1604be1f602f173c5fb67582e647fcef6c40
Date: 2025-06-13T00:26:52.696Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.4.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

I’ve been using Playwriting MCP via a container (not from Cursor’s MCP directory) and it also works completely unreliably in 1.0. It rarely can do longer sequences of commands while in 0.5 it worked much more reliably.

Not sure why the MCP “reload” icons were removed.

There is no logging, nothing to see what the orange dot means. When I stop the MCP it goes red but then it’s stuck at orange until I reload the Cursor window, just to turn orange after a (very) few interactions with the MCP. Other MCPs work OK.

Even when the MCP status dot is red, I can see it making the first request in the server logs but then it’s stuck.

3

I am running into the same issue as well after updating to version 1.0
image
Any help would be appreciated.

4

Hey, can you check the logs? To do this, open the Output panel by going to the View -> Output menu, and in the dropdown menu, select the MCP Logs.

5

I was having the same issue with the following printed in the logs:

2025-06-17 13:41:13.890 [info] ight: Starting new stdio process with command: npx @playwright/mcp@latest
2025-06-17 13:41:13.890 [error] ight: Client error for command A system error occurred (spawn npx ENOENT)

My workspace has Node installed via Mise which caused the issue for me. I’m able to work around this by creating a separate Bash script which loads the Mise environment in it and then runs the npx command.

6

Playwright is a godsend when it works. But it gets fussy several times a day.

This is probably overly heavy handed but I’ve had to keep resetting & restarting mine with this script. Not sure if something with how I use it is strange, but I am constantly getting profile related errors.

It be incredible if playwright MCP had its own tool to manage itself more.

It is wonderful and closes the loop between ai coding and browser testing beautifully. But as an automation newbie, it does get confusing, especially with all of the ways it can launch a browser.

pkill -f mcp-chrome-profile || true && pkill -f playwright || true && pkill -f chrome || true && rm -f $HOME/Library/Caches/ms-playwright/mcp-chrome-profile/SingletonLock $HOME/Library/Caches/ms-playwright/mcp-chrome-profile/SingletonCookie $HOME/Library/Caches/ms-playwright/mcp-chrome-profile/SingletonSocket && rm -rf playwright/.user-data-dir && nohup npx @playwright/mcp@latest &

7

Resolved by mcp log

** 2025-06-17 13:50:50.700 [error] user-Playwright: npm error code E401

npm error Incorrect or missing password.**

8

works on my windows machine with the following config.

"mcp-playwright": {
  "command": "npx",
  "args": [
    "-y",
    "@executeautomation/playwright-mcp-server"
  ],
  "env": {}
}