Skip to main content
Glama
merajmehrabi

Puppeteer MCP Server

by merajmehrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Puppeteer MCP Server

No user-submitted related servers found.

    Related Servers

    • Puppeteer MCP Server

      freelw
      A
      license
      B
      quality
      D
      maintenance
      Provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.
      8
      1,833 npm
      MIT

    • Puppeteer MCP Server

      lijingle1
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform browser automation including web navigation, element interaction, and screenshot capture using Puppeteer. It provides capabilities for executing JavaScript in the browser and monitoring console logs for debugging and data extraction.
      23,092 npm
      MIT

    • Puppeteer Swarm MCP

      greatSumini
      A
      license
      A
      quality
      D
      maintenance
      Enables browser automation with concurrent tab pool management using Puppeteer. Supports navigation, content extraction, screenshots, element interaction, and JavaScript execution across multiple browser tabs with auto-recovery and idle timeout features.
      11
      7 npm
      1
      MIT

    • Chrome DevTools MCP

      ctrlShiftBryan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding assistants to control and inspect a live Chrome browser through DevTools for automated testing, performance analysis, debugging, and web scraping. Provides reliable browser automation using Puppeteer with comprehensive DevTools access.
      1,026,016 npm
      3
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct browser action (click, navigate, fill, hover, etc.) with no overlap, making selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'puppeteer_' prefix followed by a clear action verb, ensuring predictability.

    Tool Count5/5

    With 8 tools covering essential browser interactions, the count is well-scoped for a focused automation server.

    Completeness4/5

    Core operations are covered, but missing explicit waiting or content extraction tools; however, puppeteer_evaluate can compensate.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources