Mcp Server For Browser Automation With Puppeteer

Automate browser interactions and take screenshots via Puppeteer MCP.

Unique: This MCP server is specifically tailored for Puppeteer, providing a unique integration for browser automation tasks.

vs others: Unlike generic automation tools, this server is built specifically for Puppeteer, offering streamlined functionality for headless browsing.

via “mcp server for browser automation and testing”

Automate browsers and run web tests via Playwright MCP.

Unique: Unlike traditional automation tools, this server uses Playwright's accessibility tree for structured page snapshots, enhancing interaction capabilities.

vs others: This MCP server offers a more structured and deterministic approach to browser automation compared to screenshot-based methods.

via “mcp server for cloud browser automation”

Run cloud browser sessions and web automation via Browserbase MCP.

Unique: This artifact uniquely combines cloud browser infrastructure with LLM-driven web automation capabilities, allowing for natural language interactions.

vs others: It stands out from alternatives by providing a dedicated MCP framework that enhances LLM capabilities specifically for web automation.

via “headless-browser-automation-via-mcp”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Wraps Puppeteer as an MCP server rather than a direct library, enabling LLM agents to invoke browser automation through standardized tool-calling protocols without managing browser lifecycle or connection pooling themselves

vs others: Provides MCP-native browser automation (compatible with Claude and other MCP clients) whereas direct Puppeteer requires custom API wrappers and manual integration into LLM tool schemas

via “live-browser-control-via-mcp-protocol”

Chrome DevTools for coding agents

Unique: Implements MCP as a standardized protocol bridge between LLM agents and Chrome DevTools, using Puppeteer as the underlying automation engine with token-optimized response formatting specifically designed for LLM context windows. The Mutex-protected single-threaded execution model ensures deterministic browser state across sequential agent actions without race conditions.

vs others: Provides standardized MCP protocol integration (vs proprietary APIs) with native support for multiple AI clients (Claude, Gemini, Cursor) and token-optimized output, whereas raw Puppeteer requires custom serialization and context management per LLM integration.

via “mcp-standardized browser control via stdio transport”

Chrome DevTools for coding agents

Unique: Implements MCP as the primary integration layer rather than REST/WebSocket APIs, with Mutex-based single-threaded execution ensuring deterministic state management across concurrent agent requests. Directly exposes Chrome DevTools Protocol (CDP) capabilities through standardized MCP tool schemas, eliminating custom integration code per AI platform.

vs others: Provides agent-agnostic browser control via MCP standard (vs Puppeteer's Node.js-only SDK or Playwright's language-specific bindings), enabling seamless integration across Claude, Gemini, and Cursor without platform-specific adapters.

via “remote-browser-automation-via-devtools-protocol”

MCP server for Chrome DevTools

Unique: Bridges MCP protocol directly to Chrome DevTools Protocol without intermediate abstraction layers like Puppeteer or Playwright, reducing dependency overhead and enabling direct access to low-level CDP capabilities. Implements streaming response handling for long-running operations through MCP's resource and tool call patterns.

vs others: Lighter-weight than Puppeteer/Playwright-based MCP servers because it eliminates the extra abstraction layer, providing direct CDP access while maintaining MCP compatibility for seamless AI agent integration.

via “stateful-browser-automation-via-mcp”

Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌

Unique: Implements MCP protocol binding for Playwright with a global browser singleton pattern, allowing LLMs to invoke 27 browser tools against a persistent page context without managing browser lifecycle — the server handles all browser state internally via BrowserToolBase inheritance and requestHandler.ts dispatch logic

vs others: Simpler than Selenium Grid or Puppeteer clusters for LLM integration because it abstracts browser lifecycle entirely behind MCP tools, eliminating the need for agents to manage WebDriver sessions or connection pooling

via “mcp-compliant browser automation server”

** - An MCP server using Playwright for browser automation and webscrapping

Unique: Bridges Playwright's rich browser automation API directly into the MCP protocol ecosystem, enabling Claude and other MCP clients to perform browser control without custom wrapper code. Uses MCP's tool definition schema to expose Playwright methods as callable functions with structured parameters and responses.

vs others: Tighter integration with Claude's MCP ecosystem than generic Playwright REST wrappers, with native support for Claude's tool-calling semantics and no additional API abstraction layer.

via “mcp protocol bridging via native messaging”

Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.

Unique: Operates within the user's existing Chrome session (preserving login states and environment) rather than launching isolated browser instances like Playwright; uses native messaging for low-latency bidirectional communication between extension and Node.js server, enabling real-time tool execution without context serialization overhead

vs others: Faster and more stateful than Playwright-based solutions because it reuses the user's authenticated browser session and avoids the overhead of launching new browser instances per request

via “browser-automation-via-mcp-protocol”

Model Context Protocol servers for Playwright

Unique: Implements Playwright automation as an MCP server, enabling LLMs to control browsers through standardized protocol bindings rather than direct SDK imports, allowing stateless, language-agnostic integration with any MCP-compatible client without requiring application-level Playwright knowledge

vs others: Unlike direct Playwright SDK usage, this MCP approach decouples the LLM from browser control infrastructure, enabling multi-client automation and easier deployment in restricted environments where direct library imports are unavailable

via “remote browser session orchestration via mcp protocol”

BrowserStack's Official MCP Server

Unique: First official MCP server from BrowserStack that bridges Claude/MCP clients directly to real device cloud infrastructure; implements MCP tool schema for 2000+ device combinations without requiring developers to write Selenium/WebDriver code

vs others: Tighter integration than generic Selenium MCP wrappers because it's BrowserStack-native, with pre-built device capability definitions and optimized session management for the cloud platform

via “headless-browser-automation-via-mcp”

Fork and update (v0.6.5) of the original @modelcontextprotocol/server-puppeteer MCP server for browser automation using Puppeteer.

Unique: Wraps Puppeteer as an MCP server rather than a direct library, enabling LLM agents to invoke browser automation through standardized MCP tool/resource endpoints without language-specific SDK dependencies. Uses MCP's stdio transport for process-level isolation and multi-client support.

vs others: Provides standardized MCP interface for browser automation (vs. Puppeteer's direct Node.js API), making it compatible with any MCP client including Claude Desktop, while maintaining full Puppeteer capability surface.

via “headless-browser-automation-with-puppeteer”

Puppeteer+ MarTech - Enhanced Puppeteer MCP server with specialized digital marketing analytics capabilities. This builds upon the official @modelcontextprotocol/server-puppeteer with tools for analyzing marketing technologies, analytics platforms, tag ma

Unique: Wraps Puppeteer's CDP bindings as an MCP server, allowing LLM agents to treat browser automation as a first-class tool with structured input/output schemas rather than requiring custom integration code

vs others: Tighter LLM integration than standalone Puppeteer scripts because MCP standardizes tool discovery and parameter validation, reducing boilerplate for multi-step browser workflows

via “cross-platform browser session management via puppeteer”

** (by UI-TARS) - A fast, lightweight MCP server that empowers LLMs with browser automation via Puppeteer’s structured accessibility data, featuring optional vision mode for complex visual understanding and flexible, cross-platform configuration.

Unique: Leverages Puppeteer's context API for true session isolation rather than simple page management, enabling concurrent multi-session automation with independent cookies/storage while maintaining a single browser process for resource efficiency

vs others: More efficient than spawning separate browser processes per session; provides better isolation than shared-page approaches; cross-platform without custom OS-specific code unlike Selenium or raw browser APIs

via “cloud-based browser automation via mcp”

** - Automate browser interactions in the cloud (e.g. web navigation, data extraction, form filling, and more)

Unique: Implements browser automation as a first-class MCP tool, enabling seamless integration into LLM agent loops without custom orchestration code. Uses Browserbase's managed cloud browser pool to handle session lifecycle, resource cleanup, and concurrent request queuing, eliminating the need for developers to manage Playwright/Puppeteer instances or handle browser crashes.

vs others: Simpler than Playwright/Selenium for agent workflows because it abstracts infrastructure management and integrates natively with MCP-compatible LLM frameworks, while being more flexible than REST-only web scraping APIs by supporting interactive workflows (form submission, JavaScript execution, dynamic waits).

via “playwright-based web content crawling with mcp server interface”

A command-line tool acting as an MCP (ModelContextProtocol) server, using Playwright to crawl web content for AI models.

Unique: Implements MCP server protocol as the primary interface layer, allowing direct tool invocation from MCP-compatible AI models without requiring custom API wrappers or client code — Playwright handles browser lifecycle management transparently within the MCP server process

vs others: Simpler integration than building custom REST APIs around Playwright; native MCP support means Claude and compatible models can call crawling directly without intermediate orchestration layers

via “headless-browser-automation-via-mcp”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Bridges Puppeteer's browser automation directly into the MCP protocol ecosystem, enabling LLM agents to invoke browser actions as first-class tools without custom integration code. Implements MCP server scaffolding that maps Puppeteer methods to standardized tool definitions.

vs others: Simpler than building custom Puppeteer integrations for each MCP client because it standardizes browser automation as a reusable MCP service; lighter-weight than Selenium-based MCP servers due to Puppeteer's DevTools Protocol efficiency.

via “browser-automation-via-mcp-protocol”

** - Playwright MCP server

Unique: Bridges Playwright's cross-browser automation with Claude's native MCP tool-calling interface, eliminating the need for custom agent scaffolding code — the MCP server acts as a standardized adapter that maps LLM function calls directly to Playwright API methods with automatic context management.

vs others: Unlike Selenium-based MCP servers or custom Playwright wrappers, this provides native integration with Claude's MCP ecosystem, reducing integration complexity and enabling seamless multi-turn agent workflows without custom glue code.

via “headless-browser-automation-via-mcp”

Experimental MCP server for browser automation using Puppeteer (inspired by @modelcontextprotocol/server-puppeteer)

Unique: Implements MCP server transport layer specifically for Puppeteer, enabling direct LLM agent control of browser automation without custom integration code. Uses MCP's standardized tool schema to expose Puppeteer methods as callable functions, with built-in screenshot and DOM evaluation capabilities for agent feedback.

vs others: Provides MCP-native browser automation (compatible with Claude and other MCP clients) whereas raw Puppeteer requires custom API wrappers; simpler integration than Selenium-based MCP servers due to Puppeteer's JavaScript-native design.