Skip to main content
Glama
hooplus1ce

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to DrissionPage-MCP

No user-submitted related servers found.

    Related Servers

    • chrome-mcp

      xiyiyiru
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.
      7
      GPL 3.0

    • DrissionPageMCP

      wxhzhwxhzh
      F
      license
      C
      quality
      D
      maintenance
      Provides browser automation via DrissionPage and FastMCP, enabling AI to control Chrome browsers for tasks like page navigation, element interaction, JavaScript execution, and network monitoring.
      29
      243
      -

    • 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

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3.4/5.0

    Scored across 56 tools

    Disambiguation5/5

    Each tool has a very distinct purpose, even within the large VTable group where tools target different actions like reading, finding, clicking, editing, and hovering. There is minimal functional overlap that would confuse an agent.

    Naming Consistency2/5

    Naming conventions are mixed: some tools use verb-first patterns (get_page_html, find_element), while many use object-first patterns (browser_launch, cookies_get, vtable_read_cells). This inconsistency, though readable, fails to follow a single predictable scheme.

    Tool Count1/5

    With 56 tools, the server vastly exceeds the typical range. Even for a specialized VTable browser automation server, many tools could be consolidated (e.g., cell_info, cell_text, cell_state), making the surface area unwieldy.

    Completeness5/5

    The toolset comprehensively covers browser lifecycle, navigation, tab management, element interactions, iframes, cookies, multi-account contexts, and an exceptionally deep set of VTable-specific operations including selection, scrolling, editing, and visual state inspection.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources