Skip to main content
Glama
browsermcp
by conradkoh

Related Servers

Alternatives to browsermcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI agents to control an anti-detection browser for navigation, interaction, search, extraction, downloads, multi-tab workflows, and persistent sessions. Supports stdio and HTTP transports for desktop or remote MCP clients.
      971 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Multi-agent local browser automation MCP server with per-agent WebSocket paths, configurable ports, and fixes for upstream issues like port collisions and recursion bugs.
      23
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Standalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.
      25 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that wraps sendblue-browser-use's HTTP API, providing tools to control a stealth-patched Chromium browser with persistent sessions, navigation, screenshots, and script execution.
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This server enables MCP clients and AI agents to perform browser automation with Playwright-compatible tools, persistent profiles, extensions, proxy support, and humanized interactions. It can be run via npm or Docker over stdio or Streamable HTTP for web research, automation, testing, and regional QA.
      541 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct action (click, hover, type, navigate, etc.) with no overlap. Even similar actions like go_back and go_forward are clearly differentiated by direction.

    Naming Consistency5/5

    All tools follow a consistent `browser_<verb>` pattern in snake_case. The verbs are intuitive and match the action (e.g., browser_navigate, browser_type).

    Tool Count5/5

    12 tools is appropriate for browser automation, covering navigation, interaction, screenshots, and debugging without being overwhelming or sparse.

    Completeness4/5

    The set covers core browsing interactions and debugging. Missing a refresh or scroll action, but most essential workflows are possible.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues