Browser[X]MCP
Related Servers
Alternatives to Browser[X]MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables AI to control browsers via natural language for web automation, testing, and data scraping. Supports Chrome-based browsers and integrates with any MCP-compatible AI tool.172-
- FlicenseCqualityDmaintenanceEnables browser automation, including navigation, form filling, login with CAPTCHA handling, and element manipulation, using a Chrome-based MCP server.364-
- FlicenseNot gradedqualityDmaintenanceAI-driven smart browser automation MCP server supporting multiple AI providers. Enables natural language element selection and self-healing for robust web automation.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform deterministic Windows desktop and browser automation through MCP, using pre-validated UI Automation and DOM locators for fast, stable execution of ERP and business workflows.2MIT
- FlicenseNot gradedqualityBmaintenanceEnables browser automation with AI agent support and secure credential management through 20 MCP tools, accessible via stdio or HTTP bridge.-
- AlicenseAqualityCmaintenanceMCP server providing browser automation for AI agents, enabling actions like clicking and typing, structured data extraction, content validation, multi-step task execution, and memory enrichment from web pages.8235 npmMIT
TDQS
Scored across 14 tools
Most tools target distinct actions (navigate, input, scroll, start, etc.), and the two-step element workflow is clear. However, click_element_by_xpath and execute_atomic_action both can perform clicks, and evaluate_in_page could also replicate any action, creating minor overlap. Descriptions mostly clarify but ambiguity exists in action execution tools.
Almost all tools follow snake_case verb_noun pattern, with verbs like extract, navigate, input, scroll, start, list, get, execute, evaluate, click. Inconsistencies: 'compare_with_screenshot' uses preposition structure, and 'batch_actions' uses a noun as verb, but overall readable and predictable.
14 tools is within the ideal range for a browser automation server, covering navigation, interaction, element inspection, and performance utilities without feeling bloated.
The set covers navigation, interaction, element inspection, and even performance testing, but lacks a browser shutdown/close tool and explicit waiting/synchronization operations, which are common in browser automation. Core workflows are present but the lifecycle is incomplete.