Skip to main content
Glama
DevHusnainAi

ZeroDOM

by DevHusnainAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ZeroDOM

No user-submitted related servers found.

    Related Servers

    • Plasmate by plasmate-labs

      Plasmateofficial

      plasmate-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Agent-native headless browser for AI agents. Converts web pages to a Semantic Object Model (SOM) instead of raw HTML — 17x average token reduction across real-world sites (up to 117x on complex pages). Native MCP server with fetch_page, extract_text, extract_links, and full browser automation. No API key required.
      28 npm
      Apache 2.0

    • Rove

      noncelogic
      A
      license
      C
      quality
      C
      maintenance
      Hosted Playwright browser automation for AI agents. Returns accessibility trees instead of screenshots, cutting token usage by 77%. Navigate, interact, extract structured data, and take screenshots — all via MCP. Zero infrastructure, credit-based pricing.
      6
      50 npm
      MIT

    • Browser MCP

      drisplabs
      A
      license
      A
      quality
      A
      maintenance
      Gives AI agents a compact, semantic interface to the browser, returning structured page snapshots with stable element IDs instead of raw DOM. Enables agents to navigate, interact, and extract information from web pages efficiently.
      6
      26
      7 npm
      17
      MIT
    • BAP MCP by browseragentprotocol

      BAP MCPofficial

      browseragentprotocol
      A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight browser automation server for AI agents, enabling fast (10-25ms per action), structured observations and semantic selectors with zero token overhead.
      6
      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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: navigation, reading, searching, clicking, and filling. No overlap in purpose; descriptions clearly differentiate their use cases.

    Naming Consistency5/5

    All tools follow a consistent zerodom_verb_noun pattern (click_node, parse_url, read_page, find, fill_node). Naming is predictable and uniform, making the set easy to navigate.

    Tool Count5/5

    Five tools is well-scoped for a DOM interaction server, covering core navigation, reading, searching, and action tasks without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full lifecycle: navigating to a page, reading current state, searching within it, and performing actions (click, fill). No obvious dead ends or missing essential operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources