Skip to main content
Glama

Related Servers

Alternatives to turbo-browser-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation and web page interaction through Playwright's accessibility tree, allowing LLMs to navigate, fill forms, click elements, and extract content without requiring vision models or screenshots.
      10,908,336 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a real Chromium browser through the upstream Playwright tool surface for web research, automation, and testing, with persistent login profiles, humanized mouse/keyboard/scroll behavior, and proxy matching for regional QA. Ships via npm or Docker over stdio or Streamable HTTP, so clients like Claude Desktop, Codex CLI, and Cursor can connect in minutes.
      280 npm
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables browser automation and web interaction through structured accessibility snapshots using Playwright. Supports clicking, typing, navigation, form filling, and other web actions without requiring screenshots or vision models.
      10,908,336 npm
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform Playwright-compatible browser automation through unchanged upstream tools, using a Chromium runtime with persistent profiles, proxy matching, humanized interactions, and Docker or stdio/Streamable HTTP deployment options.
      280 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: inspection, extraction, diagnostics, capture, storage, and human-wait are well separated. Some overlap exists between act_fast (single action), batch_actions (ordered actions including navigation/extraction), and smart_fill_form (multi-field filling), while navigation also appears inside tabs_batch, but the descriptions generally clarify when to use each.

    Naming Consistency3/5

    All names use snake_case, but the conventions are mixed: some are verb_noun (extract_clean_text, capture_page), some noun_noun (page_diagnostics, network_session), and some adjective_verb or noun_verb (smart_fill_form, act_fast, tabs_batch). The names are readable but not a predictable pattern throughout.

    Tool Count5/5

    Eleven tools is well-scoped for a browser automation server. The set covers tab management, inspection, actions, extraction, diagnostics, capture, storage/network control, and human handoff without excessive fragmentation.

    Completeness4/5

    The surface covers the major browser automation lifecycle: tabs, element discovery, form filling, actions, batching, text extraction, JS evaluation, diagnostics, screenshots/PDFs, cookies/storage, and human-in-the-loop waiting. Minor gaps remain for explicit scroll/drag/keyboard primitives, but these may be handled through act_fast or evaluate_js.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues