Skip to main content
Glama

Related Servers

Alternatives to OpenTabs

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that enables AI coding assistants to drive the real, already-logged-in Chrome browser — navigating pages, clicking, typing, reading content, taking screenshots, and inspecting tabs, cookies, and network traffic through natural language. It works as a Chrome extension, so no remote-debugging port needs to be opened and pages the user is already signed into are fully usable.
      3 npm
      ISC
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding tools drive the user's real, already-logged-in Chrome — reading pages, clicking, typing, uploading files, taking screenshots, and inspecting tabs, cookies, console, and network traffic — via 25 browser automation tools that pass bot detection without a debugging port. Requires a companion Chrome extension and stays entirely on the user's machine.
      3 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that lets AI coding assistants drive the user's own already-signed-in Chrome, so agents can read logged-in pages, click, fill forms, navigate, screenshot, inspect network traffic and storage, and run multi-step browser workflows without a separate headless browser or remote debugging port. All communication stays on the user's machine and agent-opened tabs are grouped so they never steal focus.
      3 npm
      ISC

    TDQS

    A3.8/5.0

    Scored across 42 tools

    Disambiguation4/5

    Tools are logically grouped by prefix (browser_, extension_, plugin_) with distinct purposes within each domain. While some similarity exists between content retrieval tools (browser_get_page_html vs browser_get_tab_content vs browser_get_resource_content), the descriptions clearly differentiate raw HTML, visible text, and cached resources respectively.

    Naming Consistency5/5

    All 42 tools follow a rigorous snake_case convention with consistent prefix_verb_noun structure (e.g., browser_click_element, extension_get_state, plugin_analyze_site). No mixing of camelCase or kebab-case; verb choices are standardized across the surface.

    Tool Count2/5

    At 42 tools, this significantly exceeds the 25+ threshold defined as 'too many' for appropriate scope. While the server covers browser automation, extension management, and plugin development, the surface is bloated with granular single-purpose tools that could potentially be consolidated (e.g., paired enable/disable operations).

    Completeness4/5

    Comprehensive coverage across all three domains: full browser lifecycle and interaction (tabs, navigation, DOM, network, storage), extension debugging and control, and plugin security review workflows. Minor gaps include lack of localStorage/sessionStorage modification (only get) and absence of bulk cookie operations.

    Maintenance

    ActivityStale
    ResponsivenessWithin a week