What can onestep-puppeteer-mcp-server do?

headless-browser-automation-via-mcp, page-navigation-and-content-retrieval, dom-element-interaction-and-selection, screenshot-and-visual-capture, page-content-evaluation-and-javascript-execution, mcp-protocol-transport-and-tool-discovery, browser-lifecycle-management, cookie-and-session-management

onestep-puppeteer-mcp-server

MCP ServerFree

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

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

headless-browser-automation-via-mcp

Medium confidence

Exposes Puppeteer browser automation capabilities through the Model Context Protocol (MCP), allowing LLM agents to control headless Chrome/Chromium instances via standardized tool calls. Implements MCP server transport layer that translates LLM function-calling requests into Puppeteer API invocations, managing browser lifecycle (launch, navigation, interaction) and returning structured results back to the agent context.

Solves for

I want my LLM agent to autonomously navigate websites and extract data without writing custom browser control codeI need to automate web scraping, form filling, and screenshot capture triggered by LLM reasoningI want to integrate browser automation into an agentic workflow where the LLM decides what web actions to take

Best for

LLM application developers building autonomous web agents

Teams integrating Puppeteer automation into Claude/GPT-based workflows

Researchers prototyping browser-based task automation with language models

Requires

Node.js 14+ (Puppeteer compatibility)

MCP client implementation (e.g., Claude Desktop, custom MCP client)

Chrome/Chromium binary or Puppeteer bundled Chromium

Limitations

Experimental/unstable — not production-ready, API may change without notice

Single browser instance per MCP server process — no built-in multi-browser concurrency management

No persistent session state across MCP server restarts — browser context is ephemeral

What makes it unique

Bridges Puppeteer directly into MCP protocol, enabling LLM agents to invoke browser automation as first-class tools without custom wrapper code. Implements MCP resource/tool discovery so agents can introspect available browser capabilities.

vs alternatives

Simpler integration than building custom Puppeteer API wrappers for each LLM framework; MCP standardization allows the same server to work with any MCP-compatible client (Claude, custom agents, etc.)

page-navigation-and-content-retrieval

Medium confidence

Implements Puppeteer navigation primitives (goto, reload, back, forward) with configurable wait conditions (networkidle, domcontentloaded, load) and returns full page content (HTML, text, metadata). Handles navigation timeouts, error states, and page load detection to ensure reliable content retrieval before proceeding with further automation steps.

Solves for

I want to navigate to a URL and wait for the page to fully load before extracting dataI need to handle navigation failures gracefully and retry or report errors to the agentI want to retrieve both raw HTML and extracted text content from a page for analysis

Best for

Web scraping workflows where page load state matters

Multi-step navigation scenarios (crawling site hierarchies)

Agents that need to verify page state before proceeding

Requires

Active Puppeteer browser instance

Valid URL or page context from prior navigation

Network connectivity for remote URLs

Limitations

No built-in JavaScript execution context inspection — can't directly query page state from agent

Wait conditions are Puppeteer defaults — no custom wait logic (e.g., wait for specific element visibility)

Large pages (>10MB HTML) may cause memory pressure or slow content return

What makes it unique

Exposes Puppeteer's wait-condition logic through MCP, allowing agents to specify load-readiness criteria (networkidle, domcontentloaded) rather than fixed delays. Returns structured page metadata alongside content.

vs alternatives

More reliable than simple HTTP clients for JavaScript-heavy sites; wait conditions prevent race conditions where agent tries to extract data before page renders

dom-element-interaction-and-selection

Medium confidence

Provides CSS/XPath selector-based element interaction (click, type, focus, hover) and element property retrieval (text, attributes, visibility). Uses Puppeteer's page.$(selector) and page.$$(selector) for element discovery, then invokes actions with error handling for missing/invisible elements. Returns interaction results and element state snapshots to the agent.

Solves for

I want to click buttons, fill form fields, and submit forms based on page structureI need to find elements by CSS selector or XPath and verify they exist before interactingI want to extract element attributes, text content, and visibility state for conditional logic

Best for

Form automation and web application testing

Dynamic page interaction where agent must locate and act on elements

Workflows requiring element state inspection before action

Requires

Active Puppeteer page context

Valid CSS selector or XPath expression

Target element must exist in DOM (may be hidden)

Limitations

Selector-based interaction requires agent to know or infer correct CSS/XPath selectors

No built-in accessibility tree parsing — can't easily discover interactive elements by role/label

Invisible/hidden elements may be selectable but not interactable — no automatic visibility validation

What makes it unique

Wraps Puppeteer element APIs (page.$, page.$$, element.click, element.type) as discrete MCP tools, allowing agents to compose multi-step interactions. Includes element property introspection (text, attributes, visibility) for conditional branching.

vs alternatives

More granular than Selenium/Playwright wrappers that often batch operations; allows agents to inspect element state between actions for adaptive behavior

screenshot-and-visual-capture

Medium confidence

Captures full-page or viewport screenshots via Puppeteer's page.screenshot() with configurable options (format, quality, clip region). Returns images as base64-encoded strings or file paths, enabling agents to visually inspect page state or verify automation results. Supports full-page scrolling capture and region-specific screenshots.

Solves for

I want to capture a screenshot of the current page state for visual verification or loggingI need to take a screenshot of a specific region (e.g., form, modal) for analysisI want to generate visual evidence of automation steps for debugging or reporting

Best for

Visual testing and verification workflows

Debugging agent behavior by inspecting rendered page state

Generating reports or audit trails with visual evidence

Requires

Active Puppeteer page context

Sufficient memory for image buffer (typically 1-10MB per screenshot)

Optional: file system access if returning file paths instead of base64

Limitations

Screenshots are static — no interactive element detection from image alone

Large full-page screenshots can be memory-intensive (100+ MB for very long pages)

Base64 encoding adds ~33% size overhead vs binary format

What makes it unique

Integrates Puppeteer screenshot capability into MCP, allowing agents to request visual snapshots as part of automation workflows. Supports both full-page and region-specific captures with configurable output formats.

vs alternatives

More flexible than static screenshot tools; agents can request screenshots at any point in a workflow to verify state or debug failures

page-content-evaluation-and-javascript-execution

Medium confidence

Executes arbitrary JavaScript in the page context via Puppeteer's page.evaluate() and page.evaluateHandle(), returning serialized results. Enables agents to run custom scripts for data extraction, DOM manipulation, or state inspection without separate tool calls. Handles serialization of return values (primitives, objects, arrays) and error propagation.

Solves for

I want to run custom JavaScript to extract complex data structures from the pageI need to execute page-specific logic (e.g., trigger React state updates) before extracting dataI want to inspect JavaScript runtime state (window variables, computed styles) for conditional logic

Best for

Complex data extraction from JavaScript-heavy applications

Workflows requiring page-specific custom logic

Agents that need to inspect or manipulate page state programmatically

Requires

Active Puppeteer page context

JavaScript code as string (agent must generate or provide)

Return value must be JSON-serializable

Limitations

JavaScript execution is sandboxed to page context — can't access Node.js APIs or external resources

Return values must be serializable (JSON-compatible) — functions, DOM nodes, etc. cannot be returned

No timeout enforcement on evaluate() calls — long-running scripts can block the agent

What makes it unique

Exposes Puppeteer's page.evaluate() as an MCP tool, allowing agents to execute arbitrary JavaScript in the page context. Handles serialization and error propagation transparently.

vs alternatives

More powerful than selector-based extraction for complex DOM structures; agents can run custom logic without leaving the browser context

mcp-protocol-transport-and-tool-discovery

Medium confidence

Implements MCP server transport layer (stdio or HTTP) that exposes browser automation capabilities as discoverable tools and resources. Handles MCP protocol handshake, tool schema definition, and request/response marshaling. Allows MCP clients (Claude, custom agents) to discover available browser operations and invoke them with type-safe parameters.

Solves for

I want to integrate this browser automation server with my MCP client without custom protocol codeI need to discover what browser operations are available and their parameter schemasI want to invoke browser automation tools from my LLM agent using standard MCP function calling

Best for

Developers building MCP-compatible LLM agents

Teams using Claude Desktop or other MCP clients

Researchers prototyping agent workflows with standardized tool interfaces

Requires

MCP client implementation (Claude Desktop, custom MCP client library)

Node.js runtime for MCP server process

Network connectivity (stdio or HTTP transport)

Limitations

MCP protocol overhead adds latency (~50-100ms per tool call for serialization/deserialization)

No built-in authentication — MCP server is accessible to any client with network access

Tool schemas are static — no dynamic capability discovery based on browser state

What makes it unique

Implements full MCP server stack (protocol handling, tool schema registration, request marshaling) for Puppeteer, abstracting away transport details. Enables seamless integration with any MCP-compatible client.

vs alternatives

Standardized MCP interface allows the same server to work with multiple clients (Claude, custom agents); avoids custom protocol/API design

browser-lifecycle-management

Medium confidence

Manages browser instance lifecycle (launch, close, context creation) through MCP tool calls. Handles browser initialization with configurable options (headless mode, viewport size, user agent) and graceful shutdown. Maintains single browser instance per server process with context isolation for multi-step workflows.

Solves for

I want to start a browser instance with specific configuration (headless, viewport, user agent)I need to cleanly close the browser and release resources when automation is completeI want to create isolated browser contexts for parallel or independent workflows

Best for

Long-running agent workflows that need persistent browser state

Scenarios requiring specific browser configuration (viewport, user agent)

Multi-step automation where browser context must survive across tool calls

Requires

Node.js process with sufficient memory (100-300MB per browser)

Chrome/Chromium binary or Puppeteer bundled Chromium

File system access for browser cache/data directories

Limitations

Single browser instance per server — no built-in multi-browser concurrency

Browser launch is synchronous and blocking — can take 2-5 seconds per instance

No automatic browser restart on crash — manual recovery required

What makes it unique

Exposes Puppeteer browser lifecycle as MCP tools, allowing agents to control browser startup/shutdown as part of workflows. Manages single persistent instance across multiple tool calls.

vs alternatives

Simpler than managing browser instances externally; agents can request browser operations without worrying about process management

cookie-and-session-management

Medium confidence

Provides tools to get, set, and delete cookies and local storage via Puppeteer's page.cookies() and page.evaluate() APIs. Enables agents to persist authentication state, manage sessions, and handle cookie-based workflows. Supports cookie serialization/deserialization for cross-session reuse.

Solves for

I want to log in once and reuse the session across multiple page navigationsI need to set specific cookies (e.g., tracking, preferences) before navigating to a pageI want to extract and store cookies for later session restoration

Best for

Multi-step workflows requiring persistent authentication

Scenarios where login state must be preserved across agent steps

Testing workflows that need to simulate returning users

Requires

Active Puppeteer browser instance

Page context (cookies are per-page/domain)

Valid cookie format (name, value, domain, path, etc.)

Limitations

Cookies are browser-instance-specific — not persisted across server restarts

No built-in cookie encryption — sensitive data (auth tokens) stored in plain text

Local storage access requires JavaScript execution — more complex than cookie APIs

What makes it unique

Wraps Puppeteer cookie APIs as MCP tools, enabling agents to manage session state as part of automation workflows. Supports cookie serialization for cross-session persistence.

vs alternatives

More convenient than manual HTTP header manipulation; agents can work with cookies at the browser level where they're naturally managed

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with onestep-puppeteer-mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server31

puppeteer-mcp-server

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

webpage-navigation-and-interactionheadless-browser-automation-via-mcp

2 shared capabilities

MCP Server27

@hisma/server-puppeteer

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

dom-element-interaction-and-manipulationheadless-browser-automation-via-mcp

2 shared capabilities

MCP Server21

Puppeteer

** - Browser automation and web scraping.

headless-browser-automation-via-mcpweb-page-navigation-and-interaction

2 shared capabilities

MCP Server25

puppeteer-mcp-server

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

dom-element-interaction-and-queryingheadless-browser-automation-via-mcp

2 shared capabilities

MCP Server25

@mseep/puppeteer-mcp-server

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

dom-element-interaction-via-selectorsheadless-browser-automation-via-mcp

2 shared capabilities

MCP Server24

@todoforai/puppeteer-mcp-server

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

page-navigation-and-interactionheadless-browser-automation-via-mcp

2 shared capabilities

Best For

✓LLM application developers building autonomous web agents
✓Teams integrating Puppeteer automation into Claude/GPT-based workflows
✓Researchers prototyping browser-based task automation with language models
✓Web scraping workflows where page load state matters
✓Multi-step navigation scenarios (crawling site hierarchies)
✓Agents that need to verify page state before proceeding
✓Form automation and web application testing
✓Dynamic page interaction where agent must locate and act on elements

Known Limitations

⚠Experimental/unstable — not production-ready, API may change without notice
⚠Single browser instance per MCP server process — no built-in multi-browser concurrency management
⚠No persistent session state across MCP server restarts — browser context is ephemeral
⚠Puppeteer requires significant memory overhead (typically 100-300MB per browser instance)
⚠No built-in timeout or resource limits — long-running automation can exhaust system resources
⚠No built-in JavaScript execution context inspection — can't directly query page state from agent

Requirements

Node.js 14+ (Puppeteer compatibility)MCP client implementation (e.g., Claude Desktop, custom MCP client)Chrome/Chromium binary or Puppeteer bundled ChromiumSufficient system memory for headless browser instancesActive Puppeteer browser instanceValid URL or page context from prior navigationNetwork connectivity for remote URLsActive Puppeteer page context

Input / Output

Accepts: text (URLs, selectors, text input), structured data (navigation parameters, form field mappings), text (URL string), text (navigation options: waitUntil, timeout), text (CSS selector or XPath), text (input text for typing), structured data (interaction options: delay, timeout), structured data (screenshot options: format, quality, clip region, fullPage), text (JavaScript code as string), structured data (function arguments), structured data (MCP tool call with parameters), structured data (browser launch options: headless, viewport, userAgent, args), structured data (cookie object: name, value, domain, path, expires), text (cookie name for deletion)

Produces: text (page content, extracted text), structured data (JSON from page parsing), binary (screenshots as base64 or file paths), text (HTML content), text (extracted plain text), structured data (page metadata: title, URL, status code), text (element text content), structured data (element attributes, bounding box), boolean (visibility, interactability state), binary (image as base64 string or file path), structured data (image metadata: width, height, format), text (string results), structured data (objects, arrays, primitives), null (if script returns undefined), structured data (MCP tool result with content and metadata), structured data (browser instance metadata: pid, version), boolean (success/failure of launch or close), structured data (array of cookie objects), boolean (success of set/delete operation)

UnfragileRank

Adoption15%(30% weight)

Quality25%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit onestep-puppeteer-mcp-server→

Package Details

npm

Registry

0.5.5

Version

Weekly Downloads

About

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

Alternatives to onestep-puppeteer-mcp-server

wink-embeddings-sg-100d24Repository

100-dimensional English word embeddings for wink-nlp

Compare →

voyage-ai-provider30API

Voyage AI Provider for running Voyage AI models with Vercel AI SDK

Compare →

@vibe-agent-toolkit/rag-lancedb27Agent

LanceDB implementation of RAG interfaces for vibe-agent-toolkit

Compare →

vectra41Repository

A lightweight, file-backed vector database for Node.js and browsers with Pinecone-compatible filtering and hybrid BM25 search.

Compare →

Are you the builder of onestep-puppeteer-mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities8 decomposed

headless-browser-automation-via-mcp

Medium confidence

Solves for

Best for

LLM application developers building autonomous web agents

Teams integrating Puppeteer automation into Claude/GPT-based workflows

Researchers prototyping browser-based task automation with language models

Requires

Node.js 14+ (Puppeteer compatibility)

MCP client implementation (e.g., Claude Desktop, custom MCP client)

Chrome/Chromium binary or Puppeteer bundled Chromium

Limitations

Experimental/unstable — not production-ready, API may change without notice

Single browser instance per MCP server process — no built-in multi-browser concurrency management

No persistent session state across MCP server restarts — browser context is ephemeral

What makes it unique

vs alternatives

Simpler integration than building custom Puppeteer API wrappers for each LLM framework; MCP standardization allows the same server to work with any MCP-compatible client (Claude, custom agents, etc.)

page-navigation-and-content-retrieval

Medium confidence

Solves for

Best for

Web scraping workflows where page load state matters

Multi-step navigation scenarios (crawling site hierarchies)

Agents that need to verify page state before proceeding

Requires

Active Puppeteer browser instance

Valid URL or page context from prior navigation

Network connectivity for remote URLs

Limitations

No built-in JavaScript execution context inspection — can't directly query page state from agent

Wait conditions are Puppeteer defaults — no custom wait logic (e.g., wait for specific element visibility)

Large pages (>10MB HTML) may cause memory pressure or slow content return

What makes it unique

vs alternatives

More reliable than simple HTTP clients for JavaScript-heavy sites; wait conditions prevent race conditions where agent tries to extract data before page renders

dom-element-interaction-and-selection

Medium confidence

Solves for

Best for

Form automation and web application testing

Dynamic page interaction where agent must locate and act on elements

Workflows requiring element state inspection before action

Requires

Active Puppeteer page context

Valid CSS selector or XPath expression

Target element must exist in DOM (may be hidden)

Limitations

Selector-based interaction requires agent to know or infer correct CSS/XPath selectors

No built-in accessibility tree parsing — can't easily discover interactive elements by role/label

Invisible/hidden elements may be selectable but not interactable — no automatic visibility validation

What makes it unique

vs alternatives

More granular than Selenium/Playwright wrappers that often batch operations; allows agents to inspect element state between actions for adaptive behavior

screenshot-and-visual-capture

Medium confidence

Solves for

Best for

Visual testing and verification workflows

Debugging agent behavior by inspecting rendered page state

Generating reports or audit trails with visual evidence

Requires

Active Puppeteer page context

Sufficient memory for image buffer (typically 1-10MB per screenshot)

Optional: file system access if returning file paths instead of base64

Limitations

Screenshots are static — no interactive element detection from image alone

Large full-page screenshots can be memory-intensive (100+ MB for very long pages)

Base64 encoding adds ~33% size overhead vs binary format

What makes it unique

vs alternatives

More flexible than static screenshot tools; agents can request screenshots at any point in a workflow to verify state or debug failures

page-content-evaluation-and-javascript-execution

Medium confidence

Solves for

Best for

Complex data extraction from JavaScript-heavy applications

Workflows requiring page-specific custom logic

Agents that need to inspect or manipulate page state programmatically

Requires

Active Puppeteer page context

JavaScript code as string (agent must generate or provide)

Return value must be JSON-serializable

Limitations

JavaScript execution is sandboxed to page context — can't access Node.js APIs or external resources

Return values must be serializable (JSON-compatible) — functions, DOM nodes, etc. cannot be returned

No timeout enforcement on evaluate() calls — long-running scripts can block the agent

What makes it unique

Exposes Puppeteer's page.evaluate() as an MCP tool, allowing agents to execute arbitrary JavaScript in the page context. Handles serialization and error propagation transparently.

vs alternatives

More powerful than selector-based extraction for complex DOM structures; agents can run custom logic without leaving the browser context

mcp-protocol-transport-and-tool-discovery

Medium confidence

Solves for

Best for

Developers building MCP-compatible LLM agents

Teams using Claude Desktop or other MCP clients

Researchers prototyping agent workflows with standardized tool interfaces

Requires

MCP client implementation (Claude Desktop, custom MCP client library)

Node.js runtime for MCP server process

Network connectivity (stdio or HTTP transport)

Limitations

MCP protocol overhead adds latency (~50-100ms per tool call for serialization/deserialization)

No built-in authentication — MCP server is accessible to any client with network access

Tool schemas are static — no dynamic capability discovery based on browser state

What makes it unique

vs alternatives

Standardized MCP interface allows the same server to work with multiple clients (Claude, custom agents); avoids custom protocol/API design

browser-lifecycle-management

Medium confidence

Solves for

Best for

Long-running agent workflows that need persistent browser state

Scenarios requiring specific browser configuration (viewport, user agent)

Multi-step automation where browser context must survive across tool calls

Requires

Node.js process with sufficient memory (100-300MB per browser)

Chrome/Chromium binary or Puppeteer bundled Chromium

File system access for browser cache/data directories

Limitations

Single browser instance per server — no built-in multi-browser concurrency

Browser launch is synchronous and blocking — can take 2-5 seconds per instance

No automatic browser restart on crash — manual recovery required

What makes it unique

Exposes Puppeteer browser lifecycle as MCP tools, allowing agents to control browser startup/shutdown as part of workflows. Manages single persistent instance across multiple tool calls.

vs alternatives

Simpler than managing browser instances externally; agents can request browser operations without worrying about process management

cookie-and-session-management

Medium confidence

Solves for

Best for

Multi-step workflows requiring persistent authentication

Scenarios where login state must be preserved across agent steps

Testing workflows that need to simulate returning users

Requires

Active Puppeteer browser instance

Page context (cookies are per-page/domain)

Valid cookie format (name, value, domain, path, etc.)

Limitations

Cookies are browser-instance-specific — not persisted across server restarts

No built-in cookie encryption — sensitive data (auth tokens) stored in plain text

Local storage access requires JavaScript execution — more complex than cookie APIs

What makes it unique

Wraps Puppeteer cookie APIs as MCP tools, enabling agents to manage session state as part of automation workflows. Supports cookie serialization for cross-session persistence.

vs alternatives

More convenient than manual HTTP header manipulation; agents can work with cookies at the browser level where they're naturally managed

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to onestep-puppeteer-mcp-server

wink-embeddings-sg-100d24Repository

100-dimensional English word embeddings for wink-nlp

Compare →

voyage-ai-provider30API

Voyage AI Provider for running Voyage AI models with Vercel AI SDK

Compare →

@vibe-agent-toolkit/rag-lancedb27Agent

LanceDB implementation of RAG interfaces for vibe-agent-toolkit

Compare →

vectra41Repository

A lightweight, file-backed vector database for Node.js and browsers with Pinecone-compatible filtering and hybrid BM25 search.

Compare →

onestep-puppeteer-mcp-server

Capabilities8 decomposed

headless-browser-automation-via-mcp

page-navigation-and-content-retrieval

dom-element-interaction-and-selection

screenshot-and-visual-capture

page-content-evaluation-and-javascript-execution

mcp-protocol-transport-and-tool-discovery

browser-lifecycle-management

cookie-and-session-management

Related Artifactssharing capabilities

puppeteer-mcp-server

@hisma/server-puppeteer

Puppeteer

puppeteer-mcp-server

@mseep/puppeteer-mcp-server

@todoforai/puppeteer-mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to onestep-puppeteer-mcp-server

Are you the builder of onestep-puppeteer-mcp-server?

Get the weekly brief

Data Sources

onestep-puppeteer-mcp-server

Capabilities8 decomposed

headless-browser-automation-via-mcp

page-navigation-and-content-retrieval

dom-element-interaction-and-selection

screenshot-and-visual-capture

page-content-evaluation-and-javascript-execution

mcp-protocol-transport-and-tool-discovery

browser-lifecycle-management

cookie-and-session-management

Related Artifactssharing capabilities

puppeteer-mcp-server

@hisma/server-puppeteer

Puppeteer

puppeteer-mcp-server

@mseep/puppeteer-mcp-server

@todoforai/puppeteer-mcp-server

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to onestep-puppeteer-mcp-server

Are you the builder of onestep-puppeteer-mcp-server?

Get the weekly brief

Data Sources