DrissionPageMCPServer_Modified
Related Servers
Alternatives to DrissionPageMCPServer_Modified
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceA 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.69111 PyPI488Apache 2.0
- FlicenseBqualityDmaintenanceAn MCP server that wraps DrissionPage to provide comprehensive browser automation tools, including tab management, element interaction, network capture, and more, with AI-friendly tool descriptions and 255 unit tests.553-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for browser automation using Puppeteer that enables AI assistants to navigate web pages, interact with UI elements, and capture screenshots. It supports comprehensive web tasks including form filling, content extraction, and executing custom JavaScript within the browser context.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for multi-engine browser automation with proxy rotation, enabling AI-driven web interaction and task execution across Camoufox, DrissionPage, and Browser Use.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceBrowser automation MCP server using Pydoll, enabling agents to navigate, observe, and interact with web pages via tools like page navigation, element clicking, and screenshot capture.1MIT
- FlicenseCqualityDmaintenanceProvides browser automation via DrissionPage and FastMCP, enabling AI to control Chrome browsers for tasks like page navigation, element interaction, JavaScript execution, and network monitoring.29243-
TDQS
Scored across 17 tools
Most tools have distinct purposes with clear boundaries, such as take_screenshot for visual capture, get_dom_tree for structural analysis, and click_element for interaction. However, some overlap exists between find_elements and get_dom_tree, as both assist in element location, which could cause minor confusion in selection. The detailed descriptions help mitigate this overlap by clarifying their specific roles.
All tool names follow a consistent snake_case pattern with clear verb_noun combinations, such as take_screenshot, get_dom_tree, and click_element. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming style or convention throughout the list.
With 17 tools, the count is slightly high but reasonable for a browser automation server, covering essential operations like navigation, interaction, and monitoring. Some tools, like get_screenshot_data and save_page_source, might be redundant or niche, but overall, the set is well-scoped for its domain without being overly bloated.
The tool set provides comprehensive coverage for browser automation, including navigation, element interaction, monitoring, and data extraction. It supports a full workflow from setup (connect_browser) to interaction (click_element, input_text) and analysis (get_dom_tree, get_network_logs), with no obvious gaps that would hinder agent operations in this domain.