Skip to main content
Glama
crmmc

DrissionPage BetterMCP

by crmmc

Related Servers

Alternatives to DrissionPage BetterMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      An MCP server providing robust browser automation tools for AI assistants, including page navigation, element interaction, and screenshot capabilities. It leverages the DrissionPage library to enable standardized DOM analysis, network monitoring, and complex web task automation.
      17
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      A professional browser automation server that enables MCP clients to perform structured web navigation, element interaction, and data extraction using the DrissionPage framework. It features 14 deterministic tools optimized for LLMs to automate web workflows efficiently without relying on vision-based models.
      69
      111 PyPI
      488
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      A comprehensive browser automation MCP server providing 149 tools across 13 capability tiers, enabling LLMs to control Chrome/Edge via CDP or BiDi protocols with features like navigation, screenshots, network interception, and more.
      72
      42 PyPI
      2
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A browser automation MCP server providing 30 tools for navigation, interaction, page information, state checks, tab management, and more, enabling natural language control of browsers via MCP-compatible clients.
      -

    TDQS

    B3.2/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: page, tab, element, keyboard, network, cookie, storage, dialog, or JS. Even similar tools like keyboard_type vs keyboard_press and page_get_text vs element_get_text are clearly separated by scope and descriptions.

    Naming Consistency4/5

    Most tools follow a consistent resource_action pattern like page_navigate, element_find, cookie_set, and storage_get. A few names break the pattern with adjectives instead of verbs, notably tab_new, frame_main, and dialog_auto.

    Tool Count2/5

    31 tools is above the heavy threshold and includes a wide spread of peripheral features like network listeners, storage, cookies, and dialogs. The count feels imbalanced because several core browser automation tools are missing while the surface is still very large.

    Completeness1/5

    The tool set has severe gaps: browser_connect is referenced by browser_quit but does not exist, and element_click, element_input, and element_select are referenced in descriptions but not provided. This makes core workflows like clicking buttons or filling forms impossible without falling back to js_execute.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues