I’m experiencing a blocking issue with the Playwright MCP server integration.
Although the MCP Playwright tools are correctly detected, tracked, and shown as available, the Cursor agent is unable to use them. Tool calls never execute.
This worked correctly in Cursor 1.7, but:
Cursor 1.7 is no longer available
Cursor 2.3 does not work at all with MCP Playwright tools
I’ve seen multiple tickets for what appears to be the same issue marked as closed, but the problem is still reproducible and unresolved.
Hey, thanks for the report. This is a known regression in Cursor 2.x, and the team is aware and working on a fix.
The issue has been confirmed by several users Playwright MCP not working on Cursor. The MCP tools show up in settings, but the agent doesn’t use them. It worked in Cursor 1.7 and up to version 2.0.77, and it broke starting with 2.0.78+.
I’ll pass this to the team to help speed up the fix.
same issue here. any updates on this?? Is this a product management issue? is there some other feature that Cursor is replacing this with?? it was really great to have the PlayWright MCP working before.
Some more specifics (for my case of this, anyway). MCP servers run by default in the sandbox, so each invocation should pop a Tool permission request. Playwright doesn’t, so it hangs. It does work if you enable Auto-run for everything, but that takes it out of the sandbox.