Skip to main content
Glama
greatSumini

Puppeteer Swarm MCP

by greatSumini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Puppeteer Swarm MCP

No user-submitted related servers found.

    Related Servers

    • Puppeteer MCP Server

      merajmehrabi
      A
      license
      A
      quality
      B
      maintenance
      Enables browser automation with Puppeteer, supporting navigation, form interactions, and connection to active Chrome instances for comprehensive web page interaction.
      8
      1,833 npm
      484
      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

    • Playwright Plus Python MCP

      MCP-Mirror
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables browser automation and web scraping through Playwright, supporting navigation, screenshots, element interaction, form filling, JavaScript execution, and content extraction.
      8
      Apache 2.0

    • 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.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: click, type, and wait_for_selector handle user interactions; navigate, get_content, and screenshot manage page navigation and content; launch, close, get_pool_status, and release_tab control browser and tab lifecycle; evaluate executes JavaScript. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb-based snake_case pattern (e.g., click, navigate, get_content, wait_for_selector). There are no deviations in style or convention, making the set predictable and easy to understand at a glance.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a Puppeteer automation server. It covers essential browser operations (launch, close), tab management (navigate, release_tab, get_pool_status), user interactions (click, type, wait_for_selector), content extraction (get_content, screenshot), and scripting (evaluate), with each tool earning its place.

    Completeness5/5

    The tool set provides complete coverage for browser automation: it includes lifecycle management (launch, close), navigation (navigate), user interactions (click, type, wait_for_selector), content handling (get_content, screenshot, evaluate), and tab pooling (get_pool_status, release_tab). No obvious gaps exist for typical Puppeteer workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources