Skip to main content
Glama
withLinda

Puppeteer Real Browser MCP Server

by withLinda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Puppeteer Real Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • Cloudflare Playwright MCP

      potlee
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Control Protocol server that enables AI assistants to control a browser, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Cloudflare Playwright MCP

      jbstanley2004
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Control Protocol server that enables AI assistants to control a browser through a set of tools, allowing them to perform web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Cloudflare Playwright MCP

      ThinAirTelematics
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Control Protocol server that enables AI assistants to control a browser through web automation tasks like navigation, typing, clicking, and taking screenshots.
      -

    • Chrome MCP Server

      lxe
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to control Chrome browsers through the Chrome DevTools Protocol, allowing for navigation, clicking, typing, and extracting page information.
      121 npm
      49
      MIT

    • Cloudflare Playwright MCP

      kathayl
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Control Protocol server that enables AI assistants to control a browser through tools for web automation tasks like navigation, typing, clicking, and taking screenshots.
      -
    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

    B3.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: navigation, interaction, content retrieval, and browser lifecycle. Even get_content and save_content_as_markdown are differentiated by returning versus saving content. No two tools overlap in function.

    Naming Consistency3/5

    Tool names mix bare verbs (click, type, wait), verb_noun pairs (get_content, find_selector), and a prefixed pair (browser_init, browser_close). While readable, the inconsistency in naming style is noticeable and lacks a single predictable pattern.

    Tool Count5/5

    With 11 tools, the count is well within the ideal range for a browser automation server. Each tool covers a core aspect of browsing without redundancy or bloat.

    Completeness3/5

    The tool set covers basic navigation, interaction, waiting, content extraction, and even captcha solving. However, common browser automation features like taking screenshots, executing JavaScript, getting the current URL/title, or handling browser history are missing, leaving some gaps for general browser use.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources