MCP Directory

How to add Puppeteer MCP Server (community) to Windsurf

Community Puppeteer MCP server that can launch a browser or attach to an existing Chrome window. Paste the config into ~/.codeium/windsurf/mcp_config.json and restart Windsurf.

Last updated June 15, 2026 · 250 · stdio · no auth

Windsurf config for Puppeteer MCP Server (community)

npx -y puppeteer-mcp-server
{
  "mcpServers": {
    "puppeteer-mcp-server-community": {
      "command": "npx",
      "args": [
        "-y",
        "puppeteer-mcp-server"
      ]
    }
  }
}

Setup steps

  1. 1Open Windsurf → Cascade → the hammer/MCP icon → Configure (or edit ~/.codeium/windsurf/mcp_config.json).
  2. 2Paste the Puppeteer MCP Server (community) config below.
  3. 3Fill in placeholder secrets, then save.
  4. 4Click Refresh in the MCP panel.
  5. 5Puppeteer MCP Server (community)'s tools become available to Cascade.

Before you start

  • Node.js 18+ (run via npx or a global install)
  • Chrome/Chromium — bundled by Puppeteer for new instances; for attach mode, an existing Chrome started with `--remote-debugging-port=9222`
  • No API key or authentication required (local stdio server)

What Puppeteer MCP Server (community) can do in Windsurf

puppeteer_connect_active_tab

Attach to an existing Chrome window running with remote debugging on port 9222 and target a non-extension tab

puppeteer_navigate

Navigate the browser to a URL

puppeteer_screenshot

Capture a screenshot of the page or a specific element

puppeteer_click

Click an element by selector

puppeteer_fill

Type text into an input field

puppeteer_select

Choose an option in a select/dropdown element

puppeteer_hover

Hover over an element

puppeteer_evaluate

Execute arbitrary JavaScript in the page context and return the result

Security

Attaching to an existing Chrome over port 9222 gives the agent full access to the user's logged-in sessions and cookies, so only enable that mode deliberately. It can run arbitrary in-page JavaScript, so untrusted target sites can attempt to influence automation.

Puppeteer MCP Server (community) + Windsurf FAQ

Where is the Windsurf config file?

Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Paste the Puppeteer MCP Server (community) config there under the "mcpServers" key and restart the client.

Is Puppeteer MCP Server (community) safe to use with Windsurf?

Attaching to an existing Chrome over port 9222 gives the agent full access to the user's logged-in sessions and cookies, so only enable that mode deliberately. It can run arbitrary in-page JavaScript, so untrusted target sites can attempt to influence automation.

Is this the official Puppeteer/Google MCP server?

No. It is a community project by Meraj Mehrabi, described as experimental and inspired by the reference @modelcontextprotocol/server-puppeteer.

How do I connect to my existing Chrome instead of a new browser?

Launch Chrome with `--remote-debugging-port=9222`, then call puppeteer_connect_active_tab. The server attaches to a non-extension tab and keeps Chrome running on disconnect.

Does it require an API key?

No. It runs locally over stdio with no authentication and drives a browser on your own machine.

View repo Full Puppeteer MCP Server (community) page