Skip to main content
Glama
namecallfilter

nodriver-mcp

by namecallfilter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nodriver-mcp

No user-submitted related servers found.

    Related Servers

    • agent-browser

      TrueNix
      A
      license
      Not graded
      quality
      B
      maintenance
      A hardened local browser MCP server that drives your existing Chrome over the DevTools Protocol, providing token-efficient Markdown extraction and stealth features to avoid trivial automation detection.
      36 npm
      1
      MIT

    • chrome-mcp

      wzxklm
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.
      107 npm
      3
      MIT

    • scout-mcp-server

      stemado
      A
      license
      A
      quality
      B
      maintenance
      MCP server for browser automation with anti-detection. Scout pages, find elements, interact with websites, and monitor network traffic from any AI client that supports the Model Context Protocol.
      21
      1
      MIT

    • browser-use-relay-mcp

      mlnima
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.
      -
    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

    A4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are generally distinct, but browser_open and scraper_run could confuse an agent: both involve navigation, though scraper_run is specifically for executing a saved scraper. Descriptions mitigate this ambiguity largely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear prefixes (browser_ and scraper_), making the purpose predictable and easy to navigate.

    Tool Count5/5

    Nine tools cover both browser interaction and scraper management without excess or deficiency, well-scoped for a focused MCP server.

    Completeness4/5

    The set covers core browser operations and CRUD-like scraper management (list, get, save, run), but lacks a delete scraper tool, which is a minor gap for full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources