Skip to main content
Glama
Akioo77

Browser MCP Server

by Akioo77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Browser Tool

      robby031
      A
      license
      Not graded
      quality
      A
      maintenance
      A Playwright-based browser automation tool for AI agents, enabling web search, navigation, scraping, and page interaction through the Model Context Protocol.
      MIT

    • MCP Browser Agent

      ashley-ha
      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

    • browser-mcp-server

      ricardodeazambuja
      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
      11 npm
      3
      MIT

    • Browser MCP Server Template

      ZuccaMuka
      A
      license
      Not graded
      quality
      C
      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.
      5 npm
      1
      MIT

    • playwright-browser-skill

      91fapiao-cn
      A
      license
      C
      quality
      F
      maintenance
      Provides 101 browser automation operations via Playwright, including navigation, interaction, content extraction, network control, and more, integrated with OpenClaw through the MCP protocol.
      100
      69
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources