Skip to main content
Glama

Related Servers

Alternatives to kimi-webbridge-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      5 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP-compatible AI agents to an anti-detection browser server so they can navigate sites, interact with pages, run searches, extract content, download files, and reuse sessions across multi-tab workflows. It exposes 47 tools over stdio or HTTP transport, letting agents automate the web without getting blocked.
      549 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.
      51
      21 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP-compatible AI agents to an anti-detection browser server, enabling navigation, interaction, search, extraction, downloads, multi-tab workflows, and persistent cookie-based sessions. Agents can automate the web through 47 tools while evading bot detection, with stdio or HTTP transport support.
      549 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.
      1
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 22 tools

    Disambiguation5/5

    Each tool targets a distinct browser concern: history, tab/session management, page reading, interaction, and capture. Even similar readers like wb_snapshot, wb_get_text, and wb_find are explicitly differentiated by intended use and output type.

    Naming Consistency4/5

    All tools share a consistent wb_ prefix and snake_case style, but a few names such as wb_status, wb_network, and wb_console are nouns rather than verb_noun commands. This is a minor deviation from the otherwise predictable pattern.

    Tool Count4/5

    22 tools is above the typical compact range, but the broad browser-automation domain justifies most entries with little duplication. It feels slightly heavy rather than bloated or sparse.

    Completeness4/5

    The tool surface covers the full browser workflow: connection checking, navigation, tab lifecycle, page reading, interaction, waiting, screenshots, network/console capture, and upload. Minor gaps like dedicated cookie or dropdown helpers exist, but agents can work around them with wb_evaluate.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing