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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago