Skip to main content
Glama

Related Servers

Alternatives to Auto-Browser

  • -
    license
    Not graded
    quality
    F
    maintenance
    This server provides cloud browser automation capabilities using Browserbase, Puppeteer, and Stagehand. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a cloud browser environment.
    1,690 npm
    3,399
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables LLMs like Claude to navigate the web through Puppeteer-based tools and Steel. Based on the Web Voyager framework, it provides tools for all the standard web actions click clicking/scrolling/typing/etc and taking screenshots.
    16
    58
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    A Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities. This agent enables Claude to interact with web content, manipulate DOM elements, execute JavaScript, and perform API requests.
    13
    10 npm
    42
    TypeScript
    Mozilla Public 2.0

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Lets coding agents drive a real headful Chromium over CDP on a remote headless box, giving each project its own persistent profile, isolated login sessions, downloads, and on-demand browser lifecycle. When a site needs a human for sign-in, a captcha, 2FA, or a passkey, the operator opens the same browser from their own machine, completes the step, and hands control back to the agent.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Automate your real Chrome browser locally with AI, supporting vision, human-like input, code execution, macros, and watchdogs.
    8 npm
    MIT

TDQS

A4/5.0

Scored across 20 tools

Disambiguation5/5

Every tool targets a distinct resource or action: sessions, tabs, downloads, auth profiles, observation, reading content, and execution. Even similar tools like observe, screenshot, get_html, and find_elements have clearly different purposes and output formats, eliminating ambiguity.

Naming Consistency5/5

All tools follow a consistent browser. prefix with verb_noun snake_case naming (list_sessions, create_session, activate_tab, save_auth_profile). Even single-word verbs like observe and screenshot are acceptable and maintain predictability.

Tool Count4/5

With 20 tools, the set is on the heavier side but justified by the breadth of browser automation: session management, tab control, page reading, actions, downloads, auth profiles, and advanced features like forking and JS evaluation. Each tool serves a distinct purpose, so the count feels appropriate for a full-featured server.

Completeness5/5

The surface covers the full lifecycle: session CRUD (create, list, get, close), observation (multiple modes), navigation and interaction (execute_action), tab management, downloads, auth profiles, and even human takeover and forking. There are no obvious dead ends; every action has a complementary read or verification tool.

Maintenance

ActivityActive
ResponsivenessWithin a week