How to fix 'Attempted to use detached frame' in Puppeteer MCP server?
Using @modelcontextprotocol/server-puppeteer with Claude Desktop or Cursor, the first page navigation works but later calls fail with 'Attempted to use detached frame' (Cursor also reports WCP error -32603). The MCP server connects successfully, and the problem occurs on macOS and Windows with Node v18.18.2. Is there a fix or workaround?
Originally asked on GitHub: https://github.com/modelcontextprotocol/servers/issues/53
5 answers
Status: this is a reported bug in @modelcontextprotocol/server-puppeteer with no fix posted in the thread. The issue was closed as NOT_PLANNED, and a maintainer later said the server was moved to the archived modelcontextprotocol/servers-archived repository and recommended using one of the maintained alternatives listed in the official integrations section of the modelcontextprotocol/servers README.
The server itself starts fine. In the thread, running
npx @modelcontextprotocol/server-puppeteermanually on Node v18.18.2 worked: it just waited for input without printing errors. The failure appears after the first page visit: later calls return 'Attempted to use detached frame', or in Cursor 'WCP error -32603: Attempted to use detached Frame'.One reporter said that after the first website visit the detached-frame error could not be fixed without quitting the Claude Desktop app and trying again. Another reporter found that a later attempt worked without changing any configuration, so the behavior is intermittent. No permanent fix was given in the thread.
General advice: if you keep using this archived server, expect to restart your client when the error appears, and plan to migrate to a maintained alternative for reliable automation.
Did this work for you?What @pbernasconi tried on GitHub (Outcome unclear)
After the first website visit, the user reported a detached-frame error that they said could not be fixed without quitting the Claude Desktop app and trying again; the thread does not state whether a retry after quitting actually succeeded.
Did this work for you?What @pbernasconi tried on GitHub (Worked)
Without changing any configuration, the user tried again at a later time and reported that it was working; no cause for the change was identified.
Did this work for you?What @pbernasconi tried on GitHub (Worked)
Ran
npx @modelcontextprotocol/server-puppeteerat the command line on Node v18.18.2; the server started and waited for input, confirming the server binary could launch without errors.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
After the MCP server connection appeared successful in the logs, the user asked Claude to open paolobernasconi.com in puppeteer and got a response saying it was not possible.
Source: https://github.com/modelcontextprotocol/servers/issues/53 (opens external site)
Did this work for you?
Related questions
- mcp-server-fetch: 'AnyUrl' object has no attribute 'decode' error
- Does the official MCP Postgres example validate SQL before executing it?
- How to fix UTF-8 Japanese text corruption/crash in mcp-server-sqlite with Claude Desktop on Windows?
- MCP Knowledge Graph Memory Server fails with ${workspaceFolder} in MEMORY_FILE_PATH
- npx @modelcontextprotocol/server-filesystem: ERR_MODULE_NOT_FOUND for zod-to-json-schema