Skip to main content
Glama
Akioo77

Browser MCP Server

by Akioo77

Related Servers

Alternatives to Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A Playwright-based browser automation tool for AI agents, enabling web search, navigation, scraping, and page interaction through the Model Context Protocol.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents such as Claude Code, Claude Desktop, and Cursor to control a real browser through Playwright, including navigation, accessibility snapshots, clicking, typing, screenshots, JavaScript execution, tab management, and dialog handling. It supports local stdio use and multi-user remote HTTP sessions with isolated browsers and persistent login state.
      24 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A browser automation agent that enables Claude to interact with web browsers through the Model Context Protocol, allowing for actions like navigating websites, manipulating elements, and managing browser state.
      2
      9
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.
      63
      17 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A browser automation MCP server with stealth mode, profile management, and multi-browser support, enabling LLMs to control browsers for tasks like navigation, data extraction, and form filling.
      7 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct browser action (e.g., click vs. check for different element types, fill vs. select for form fields). No two tools have overlapping purposes; descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb-based pattern, using lowercase snake_case for compound names (e.g., get_inputs, wait_for_selector). Single verbs like click, fill, navigate are uniform.

    Tool Count5/5

    With 21 tools, the server covers a broad range of browser automation tasks (navigation, interaction, data extraction, state management) without being excessive. Each tool serves a clear purpose within the domain.

    Completeness4/5

    The set covers core browser actions—launch, navigate, click, fill, select, scroll, screenshot, text extraction, and waiting. Minor gaps exist (e.g., handling alerts, cookies, or frame access), but the surface is largely complete for typical automation scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues