MCP serverWorkflow automation
puppeteer-real-browser-mcp-server
Turns a managed local Chrome session into an MCP browser for content-first web interaction.
Turns a managed local Chrome session into an MCP browser for content-first web interaction.
Puppeteer Real Browser MCP Server starts and owns a local Chrome process for an MCP client, exposing navigation, content reading, element lookup, clicks, typing, waits, and scrolling. It defaults to a visible browser, supports headless mode, proxies, custom Chrome paths, and dedicated profiles, and closes only the process it launched. The workflow requires reading page content before interaction, allows one browser session, and does not provide a real CAPTCHA solver.
Resource types
Use cases
Platforms
Let MCP-compatible AI agents control Windows applications, UI elements, keyboard, and mouse.
Build, deploy, and monitor continuously running agents with visual blocks.
Operating systems
Runtime
Protocols & integrations
Capabilities
Audience
Public GitHub facts last synced Jul 10, 2026.
Automate real browser pages for AI agents through a fast command-line interface.
Find, install, use, and manage agent skills across many coding assistants.