Puppeteer Real Browser MCP Server

Most browser automation work still happens through a UI a human drives. Puppeteer Real Browser MCP server moves it into the conversation instead. MCP server for safe, detection-resistant browser automation.

The short version

Give an MCP-compatible AI assistant a local Chrome browser that it can open, navigate, read, and control.

• Opens a visible browser by default, with optional headless mode
• Navigates pages and reads HTML or text
• Finds elements, clicks, types, waits, and scrolls
• Uses rebrowser-puppeteer-core and a small set of anti-detection settings
• Detects Chrome on Windows, macOS, and Linux
• Supports a custom Chrome path, proxy, and dedicated automation profile

Getting it running

Installation goes through your MCP client rather than a global install: point it at puppeteer-real-browser-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

The server publishes 12 tools. What each one is for:

• browser_init — Start or reuse the managed Chrome session
• navigate — Open a URL
• get_content — Read full-page or selected HTML/text
• find_selector — Find a CSS selector from element text
• click — Click an element
• type — Clear and type into an input
• wait — Wait for a selector, navigation, or time
• random_scroll — Scroll with varied timing and distance
• solve_captcha — Return a placeholder attempt result
• save_content_as_markdown — Save as .md; currently blocked
• browser_close — Close the managed browser and reset workflow state
• Cursor — Create .cursor/mcp.json in one project, or ~/.cursor/mcp.json for all projects:

What it needs from you

Configuration is passed through the environment: CHROME_PATH, PUPPETEER_EXECUTABLE_PATH, PROXY_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18 or newer - npm and npx (included with the normal Node.js installer) - Google Chrome or Chromium - An MCP client that can start a local stdio server Claude Desktop is available on macOS and Windows. Other MCP clients can use this server on Linux.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Puppeteer Real Browser.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Puppeteer Real Browser's toolset — browser_init, navigate, get_content and 9 more — is a fair guide to whether it matches your workflow. It is maintained by withLinda; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Puppeteer Real Browser's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.