
How to add Puppeteer MCP Server (community) to Cursor
Community Puppeteer MCP server that can launch a browser or attach to an existing Chrome window. Paste the config into ~/.cursor/mcp.json and restart Cursor.
Last updated June 15, 2026 · 250★ · stdio · no auth
Cursor 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
- 1Open Cursor → Settings → MCP → Add new MCP server (or edit ~/.cursor/mcp.json directly).
- 2Paste the Puppeteer MCP Server (community) config below into the "mcpServers" object.
- 3Fill in placeholder secrets, then save.
- 4Cursor reloads MCP servers automatically — check Settings → MCP for a green status dot.
- 5Ask Cursor to use one of Puppeteer MCP Server (community)'s tools to confirm it's connected.
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 Cursor
puppeteer_connect_active_tabAttach to an existing Chrome window running with remote debugging on port 9222 and target a non-extension tab
puppeteer_navigateNavigate the browser to a URL
puppeteer_screenshotCapture a screenshot of the page or a specific element
puppeteer_clickClick an element by selector
puppeteer_fillType text into an input field
puppeteer_selectChoose an option in a select/dropdown element
puppeteer_hoverHover over an element
puppeteer_evaluateExecute 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) + Cursor FAQ
Where is the Cursor config file?
Cursor reads MCP servers from ~/.cursor/mcp.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 Cursor?
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.