Skip to main content
Glama

Related Servers

Alternatives to OpenTabs

No user-submitted related servers found.

    Related Servers

    • 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
      B
      quality
      C
      maintenance
      Turns Chrome into a local MCP server, giving AI agents 51 browser tools to inspect DOM, automate clicks, run JavaScript, audit security and accessibility, mock APIs, extract data, record demos, and more from any MCP client.
      92
      671 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Chrome extension + MCP server. Lets coding agents (Claude Code, Codex CLI) drive your real Chrome — sessions intact, 2FA stays with the user. 26 browser tools: form fill on React/CodeMirror/Monaco, privileged fetch that bypasses page CSP, authenticated downloads, in-extension docx parsing. Battle-tested by 400+ hours of real agentic browser work before public v0.9 release.
      42 npm
      2
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Browser MCP server that connects to your existing browser, preserving sessions, passwords, and extensions, enabling AI agents to interact with web pages without bot detection.
      31
      3 npm
      1
      MIT

    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

    ActivitySlowing
    ResponsivenessWithin a week