Puppeteer Real Browser MCP Server

Created By
withLindaa year ago
Puppeteer-Real-Browser MCP Server: A Model Context Protocol (MCP) server that provides AI assistants with powerful, detection-resistant browser automation capabilities using puppeteer-real-browser.
Overview

What is Puppeteer Real Browser MCP Server?

Puppeteer Real Browser MCP Server is a Model Context Protocol (MCP) server that enables AI assistants to perform browser automation tasks with detection-resistant capabilities using puppeteer-real-browser.

How to use Puppeteer Real Browser MCP Server?

To use the server, install Node.js, then install the MCP server via npm. Configure it with your AI assistant (like Claude) and start the server to enable browser interactions.

Key features of Puppeteer Real Browser MCP Server?

  • Stealth browsing capabilities to avoid bot detection.
  • Enhanced page methods for realistic interactions.
  • Support for solving captchas and managing proxies.
  • Comprehensive toolset for various browser automation tasks.

Use cases of Puppeteer Real Browser MCP Server?

  1. Automating web browsing tasks for data extraction.
  2. Filling out forms and submitting data automatically.
  3. Taking screenshots of web pages for documentation.
  4. Interacting with web applications as a human user would.

FAQ from Puppeteer Real Browser MCP Server?

  • Does this work with headless browsers?

Yes, it supports headless mode for browser operations.

  • Can I use multiple browsers at once?

Currently, it supports one browser instance at a time.

  • What captchas can it solve?

It can solve reCAPTCHA, hCaptcha, and Cloudflare Turnstile.

  • Is this detectable by websites?

While it includes anti-detection features, no solution is completely undetectable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
withLinda
Star
2
Language
TypeScript
License
-
Tags

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago