Skip to main content
Glama
Sign In
ultrabrowse

ultrabrowse

by narekgevorgyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ultrabrowse

No user-submitted related servers found.

    Related Servers

    • jev-mcp

      legostin
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a real Chrome browser for autonomous web tasks, using fast typed decisions with calibrated confidence, human-in-the-loop questions, safety gates, and full debug traces.
      214 npm
      5
      MIT

    • jev-explorer

      lazyoft
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to delegate browser exploration to Jev by providing natural-language objectives, receiving compact evidence and source context, and continuing the same live browser session through supervisor handoffs.
      6
      Apache 2.0

    • Browser Control

      echelon-agents-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive a real headful Chrome browser using vision-first computer interactions, with support for multi-agent tab groups, password-manager-filled logins, and human handoff.
      9 npm
      MIT

    • Colibri

      t4zxxx1
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to browse the web by turning pages into compact text rows instead of screenshots, running many steps in one call, returning only what changed, and filling forms locally with a Jev-style engine that needs no API key. It is safe by default: submit, pay and delete actions require user confirmation, and passwords, cards and OTPs are never typed by the AI.
      8
      1
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly distinct: click, type_text, press_key, scroll, back, close, snapshot, screenshot, and extract each have a specific role. Some overlap exists between browse, browse_many, and extract with a goal, since all can perform autonomous browsing, but their outputs and parallelism distinguish them.

    Naming Consistency4/5

    Tool names mostly follow an imperative command style with snake_case for multi-word names like type_text, press_key, and browse_many. Minor deviations like snapshot, screenshot, and back are noun/adverb-style rather than verb_ noun, but the overall pattern is readable and predictable.

    Tool Count5/5

    11 tools is well-scoped for a browser automation server. Each tool covers a distinct aspect of browsing, reading, interacting, or tab management without excessive redundancy or an overwhelming surface.

    Completeness4/5

    The core browser lifecycle is well covered: navigation via browse/back, reading via snapshot/screenshot/extract, interaction via click/type_text/press_key/scroll, and tab handling via close. Minor gaps like reload or forward navigation are absent, but the high-level browse tool can work around many of those cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources