# Playwright mcp does not work

**URL:** <https://forum.cursor.com/t/playwright-mcp-does-not-work/103933>\
**Category:** Bug Reports\
**Created:** [June 15, 2025, 3:43am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933 "2025-06-15T03:43:00Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![powerdai](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/powerdai/32/63761_2.png) [@powerdai](https://forum.cursor.com/u/powerdai)\
**Post date:** [June 15, 2025, 3:43am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/1 "2025-06-15T03:43:00Z")

</div>

### Describe the Bug

after update to 1.0, playwright mcp does not work by [Page Not Found](https://docs.cursor.com/tools).  
The mcp shows red.

It works in 0.5 version

### Steps to Reproduce

after update to 1.0, playwright mcp does not work by [Page Not Found](https://docs.cursor.com/tools).  
The mcp shows red.

### Screenshots / Screen Recordings

 ![Screenshot 2025-06-14 at 8.38.10 PM.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/d/0da5c8855d9958009d9cef14703cf8c8393da61f.png)

### 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

---

<div class="post-metadata">

**Author:** ![CK-iRonin.IT](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ck-ironin.it/32/5622_2.png) [@CK-iRonin.IT](https://forum.cursor.com/u/CK-iRonin.IT)\
**Post date:** [June 16, 2025, 1:23pm UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/2 "2025-06-16T13:23:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![mirage\_tks](https://avatars.discourse-cdn.com/v4/letter/m/db5fbb/32.png) [@mirage\_tks](https://forum.cursor.com/u/mirage_tks)\
**Post date:** [June 16, 2025, 7:45pm UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/3 "2025-06-16T19:45:52Z")

</div>

I am running into the same issue as well after updating to version 1.0  
 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/e/d/ed7caf67c3226de445d8195e8f5ea452a2cf7e5d.png)  
Any help would be appreciated.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [June 17, 2025, 10:03am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/4 "2025-06-17T10:03:21Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![laznic](https://avatars.discourse-cdn.com/v4/letter/l/d07c76/32.png) [@laznic](https://forum.cursor.com/u/laznic)\
**Post date:** [June 17, 2025, 10:58am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/5 "2025-06-17T10:58:51Z")

</div>

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

```auto
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.

---

<div class="post-metadata">

**Author:** ![khh2025](https://avatars.discourse-cdn.com/v4/letter/k/7cd45c/32.png) [@khh2025](https://forum.cursor.com/u/khh2025)\
**Post date:** [June 17, 2025, 2:02pm UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/6 "2025-06-17T14:02:10Z")

</div>

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 &`

---

<div class="post-metadata">

**Author:** ![powerdai](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/powerdai/32/63761_2.png) [@powerdai](https://forum.cursor.com/u/powerdai)\
**Post date:** [June 17, 2025, 8:55pm UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/7 "2025-06-17T20:55:03Z")

</div>

Resolved by mcp log

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

npm error Incorrect or missing password.\*\*

---

<div class="post-metadata">

**Author:** ![fa\_dou](https://avatars.discourse-cdn.com/v4/letter/f/67e7ee/32.png) [@fa\_dou](https://forum.cursor.com/u/fa_dou)\
**Post date:** [June 25, 2025, 1:28am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/8 "2025-06-25T01:28:00Z")

</div>

works on my windows machine with the following config.

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

```

---

<div class="post-metadata">

**Author:** ![United\_English](https://avatars.discourse-cdn.com/v4/letter/u/dc4da7/32.png) [@United\_English](https://forum.cursor.com/u/United_English)\
**Post date:** [July 10, 2025, 3:33am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/9 "2025-07-10T03:33:26Z")

</div>

Hi, I also faced the same issue. How exactly did you solve it? What about the password?

---

<div class="post-metadata">

**Author:** ![etozhealkhipce](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/etozhealkhipce/32/70249_2.png) [@etozhealkhipce](https://forum.cursor.com/u/etozhealkhipce)\
**Post date:** [July 12, 2025, 9:29am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/10 "2025-07-12T09:29:54Z")

</div>

Cursor just can’t find `npx` command.  
You can see it in View → Output → MCP Logs.

You need to check where is your npx located using `where npx` on Windows or `which npx` on MacOS/Linux and fix the commands in mcp.json like this:

```auto
    "playwright": {
      "command": "C:\\Users\\user\\.nvm\\versions\\node\\v20.19.0\\bin\\npx.cmd",
      "args": ["@playwright/mcp@latest"]
    },

```

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [August 11, 2025, 9:30am UTC](https://forum.cursor.com/t/playwright-mcp-does-not-work/103933/11 "2025-08-11T09:30:39Z")

</div>

Closed on August 11, 2025, 9:30am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
