With new release 1.7.4, Playwright and DBHub MCPs are not working

[IT_Developer]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

the Playwright and DBHUB MCPs are not wokring despite these are the setting:

  "DBHub": {
      "command": "npx",
      "args": [
        "@bytebase/dbhub"
      ],
      "env": {
        "TRANSPORT": "stdio",
        "DSN": "mysql://root:admin123@localhost:3306/myDB?sslmode=disable",
        "READONLY": "false"
      }
    },
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest",
        "--host=itqan.test",
        "--ignore-https-errors"
      ]
    },

I have changed nithing but after installing the update, the MCPs are not working!

Steps to Reproduce

just add thos to the MCP confiuguration file.

Expected Behavior

it should have worked.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.4 of Cursor AI IDE

For AI issues: which model did you use?

it is nto model agnostic

[deanrie]

Hey, thanks for the report. What’s the status of those MCP servers in Cursor settings, are they red or green? If they’re red, check the logs: open View → Output and select the relevant MCP from the dropdown.

If the logs don’t help, try clearing the npx cache by deleting:

macOS/Linux: ~/.npm/_npx
Windows: %LocalAppData%/npm-cache/_npx

Then restart Cursor.

[kappu72 (Andrea)]

Hi, I have the same problem with the Supabase MCP server after updating Cursor to version 1.7.4.

Following is the error log:

^^^^^^^^^
SyntaxError: The requested module 'util' does not provide an export named 'parseArgs'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:128:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:194:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:385:24)
    at async loadESM (node:internal/process/esm_loader:88:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)

[IT_Developer]

they are red

[IT_Developer]

@deanrie

Output and select the relevant MCP from the dropdown.

[IT_Developer]

@deanrie

npx cache

i did all but still the same issue. as you can see, i have added the Chrome Devtools MCP and it is working fine!

[deanrie]

What’s your Node version? The issue might be an outdated version. I set up a connection to DBHub and it works well. If it’s not Node, let me know and I’ll pass this to the team.

[andrewh (Andrew Milich)]

Could you try once more?

[kappu72 (Andrea)]

I wanted to share that the issue I was experiencing with MCP servers like Supabase and Playwright was related to the Node.js version I was using (18.17.1). Once I switched to version 20.19.0, all the MCP servers started working again.
Thanks Andrea

[IT_Developer]

now all works but the Chrome Devtools MCP IS NOT WORKING. the node version is v22.14.0