Skip to main content
Glama
Sign In
DrissionPageMCP

DrissionPageMCP

by wxhzhwxhzh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to DrissionPageMCP

No user-submitted related servers found.

    Related Servers

    • DrissionPageMCPServer_Modified

      HyperClockUp
      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

    • DrissionPage MCP Server

      jumodada
      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
      97 PyPI
      480
      Apache 2.0

    • DrissionPage-MCP

      hooplus1ce
      F
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to drive browser automation for web navigation, element interaction, and multi-account isolation via DrissionPage 5.0.
      56
      -

    • Chrome MCP Bridge

      randyrt
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.
      1
      -

    • agent-in-browser

      Gwakko
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and MCP clients to drive real Chrome, Edge, Brave, and Firefox browsers through native automation protocols. It exposes tools for navigation, page snapshots, form filling, clicks, screenshots, console/network inspection, and tab management.
      23
      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

    C2.6/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target distinct actions like navigation, clicking, input, screenshots, and network listening. A few pairs (send_enter/send_key, screenshot/screenshot_as_file) are closely related, but descriptions make them distinguishable.

    Naming Consistency3/5

    The naming is predominantly snake_case verb phrases, but getInputElementsInfo and getSimplifiedDomTree break the convention, and input_by_xapth contains a typo. Overall it remains readable and mostly predictable.

    Tool Count2/5

    With 29 tools, the server feels over-scoped, especially with redundant screenshot/listener functions and an unrelated save_dict_to_sqlite. The count exceeds the comfortable range and could be reduced by consolidating similar tools.

    Completeness4/5

    Core browser automation workflows are covered: navigation, tabs, element interaction, JS/CDP, file transfer, screenshots, and network listening. Gaps like closing tabs or cookie management are workaroundable via run_js or run_cdp.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources