Skip to main content
Glama
jwaldor

Puppeteer MCP Server

by jwaldor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Puppeteer MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Playwright MCP Server

      vinothbhc1986
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation using Playwright, allowing LLMs to interact with web pages, take screenshots, generate test code, scrape web pages, and execute JavaScript in a real browser environment.
      11,800 npm
      MIT

    • Playwright MCP Server

      MuhammadNoman76
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation using Playwright, enabling LLMs to interact with web pages, take screenshots, scrape, and execute JavaScript.
      MIT

    • Playwright MCP Server for

      o0x1024
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform browser automation tasks including web scraping, taking screenshots, and executing JavaScript using Playwright. It facilitates real-time interaction with web pages and the generation of automated test code.
      6 npm
      MIT
    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

    C2.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: make_http_request performs general HTTP requests, puppeteer_navigate navigates to URLs in a browser context, puppeteer_page_history retrieves navigation history, and semantic_search_requests searches within page requests. There is no overlap or ambiguity between these functions.

    Naming Consistency3/5

    The naming is mixed with no consistent pattern: make_http_request uses verb_noun format, puppeteer_navigate and puppeteer_page_history use a prefix_noun format, and semantic_search_requests uses an adjective_noun_noun format. While readable, the conventions vary without a predictable structure.

    Tool Count3/5

    With only 4 tools, the count feels thin for a Puppeteer server, which typically handles browser automation tasks like clicking, typing, or screenshotting. The tools cover basic navigation and HTTP requests but lack broader automation capabilities, making the scope borderline under-scoped.

    Completeness2/5

    For a Puppeteer server, there are significant gaps in the tool surface. Missing are core operations like interacting with page elements (e.g., click, type), evaluating scripts, taking screenshots, or managing browser contexts. The tools provided focus narrowly on navigation and HTTP requests, leaving major automation workflows uncovered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources