Skip to main content
Glama
Puppeteer MCP Server

Puppeteer MCP Server

by cploujoux

Puppeteer

A Model Context Protocol server that provides browser automation capabilities using Puppeteer. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.

Components

Tools

  • puppeteer_navigate

    • Navigate to any URL in the browser

    • Input: url (string)

  • puppeteer_screenshot

    • Capture screenshots of the entire page or specific elements

    • Inputs:

      • name (string, required): Name for the screenshot

      • selector (string, optional): CSS selector for element to screenshot

      • width (number, optional, default: 800): Screenshot width

      • height (number, optional, default: 600): Screenshot height

  • puppeteer_click

    • Click elements on the page

    • Input: selector (string): CSS selector for element to click

  • puppeteer_hover

    • Hover elements on the page

    • Input: selector (string): CSS selector for element to hover

  • puppeteer_fill

    • Fill out input fields

    • Inputs:

      • selector (string): CSS selector for input field

      • value (string): Value to fill

  • puppeteer_select

    • Select an element with SELECT tag

    • Inputs:

      • selector (string): CSS selector for element to select

      • value (string): Value to select

  • puppeteer_evaluate

    • Execute JavaScript in the browser console

    • Input: script (string): JavaScript code to execute

Resources

The server provides access to two types of resources:

  1. Console Logs (console://logs)

    • Browser console output in text format

    • Includes all console messages from the browser

  2. Screenshots (screenshot://<name>)

    • PNG images of captured screenshots

    • Accessible via the screenshot name specified during capture

Related MCP server: Puppeteer MCP Server

Key Features

  • Browser automation

  • Console log monitoring

  • Screenshot capabilities

  • JavaScript execution

  • Basic web interaction (navigation, clicking, form filling)

Configuration to use Puppeteer Server

Here's the Claude Desktop configuration to use the Puppeter server:

Docker

NOTE The docker implementation will use headless chromium, where as the NPX version will open a browser window.

{
  "mcpServers": {
    "puppeteer": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--init",
        "-e",
        "DOCKER_CONTAINER=true",
        "mcp/puppeteer"
      ]
    }
  }
}

NPX

{
  "mcpServers": {
    "puppeteer": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
    }
  }
}

Build

Docker build:

docker build -t mcp/puppeteer -f src/puppeteer/Dockerfile .

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

7 tools
puppeteer_clickC

Click an element on the page

Inputs: selector (required).

puppeteer_evaluateB

Execute JavaScript in the browser console

Inputs: script (required).

puppeteer_fillC

Fill out an input field

Inputs: selector (required), value (required).

puppeteer_hoverC

Hover an element on the page

Inputs: selector (required).

puppeteer_navigateB

Navigate to a URL

Inputs: url (required).

puppeteer_screenshotB

Take a screenshot of the current page or a specific element

Inputs: name (required), height, selector, width.

puppeteer_selectC

Select an element on the page with Select tag

Inputs: selector (required), value (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. Click, fill, hover, navigate, screenshot, evaluate, and select all target different browser automation actions with no overlap in functionality.

    Naming Consistency5/5

    All tools follow a perfect verb_noun pattern with consistent 'puppeteer_' prefix and snake_case naming. The naming convention is predictable and readable throughout the entire set.

    Tool Count5/5

    Seven tools is an excellent number for a browser automation server - enough to cover essential interactions without being overwhelming. Each tool serves a distinct, valuable purpose in the Puppeteer domain.

    Completeness4/5

    The toolset covers most essential browser automation operations including navigation, interaction, evaluation, and capture. A minor gap exists in text extraction/reading capabilities, but core workflows are well-supported for a basic Puppeteer interface.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      32
      13,875 npm
      5,682
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      19
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to automate web browsers using Puppeteer, allowing navigation, screenshots, form filling, and JavaScript execution in a real browser environment.
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Puppeteer with configurable options through environment variables, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a browser environment.
      7
      4
      MIT