Skip to main content
Glama
MadeByTokens

Browser MCP Server

by MadeByTokens

Related Servers

Alternatives to Browser MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      16 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive browser automation MCP server using Playwright, offering 50+ tools for page control, element interaction, content extraction, and more across multiple browser engines.
      18 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that fuses Playwright and browser-use for browser automation testing, offering 59 tools for AI-driven exploration and precise assertions on a shared browser instance, with built-in stealth anti-detection.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables browser automation with Playwright, offering 17 tools for navigation, session management, Chrome profile selection, and action recording.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready browser automation server that enables AI assistants to interact with web pages using tools for navigation, element interaction, and data extraction. It features a built-in Inspector UI and robust crash recovery for reliable automated testing and information retrieval.
      -
    • A
      license
      B
      quality
      D
      maintenance
      A browser automation server providing Playwright capabilities for controlling web browsers, capturing screenshots, extracting content, and performing complex interactions through an MCP interface.
      6
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 63 tools

    Disambiguation4/5

    Most tools have distinct purposes with clear boundaries, such as browser_click for clicking elements and browser_navigate for URL navigation. However, some overlap exists, like browser_click and browser_mouse_click, which could cause confusion despite different use cases (selector-based vs. coordinate-based). The descriptions help differentiate them, but the overlap is noticeable.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a 'browser_' prefix and descriptive verb_noun combinations, such as browser_get_dom and browser_start_video_recording. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming style.

    Tool Count2/5

    With 63 tools, the count is excessive for a browser automation server, making it overwhelming and likely to cause analysis paralysis for agents. While the domain is broad, a more focused set of 15-25 tools would be more manageable and appropriate for typical use cases.

    Completeness5/5

    The tool set provides comprehensive coverage for browser automation, including navigation, interaction, performance monitoring, security analysis, and media control. It supports full CRUD-like operations for web elements, network requests, and storage, with no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues