A
licenseNot graded
qualityD
maintenanceEnables AI agents to automate browser interactions using Selenium WebDriver, supporting multiple browsers and tools for navigation, clicking, typing, screenshots, and more.
635 npm
MIT
mcp-server-webdriver
Related Servers
Alternatives to mcp-server-webdriver
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to automate web browser interactions through Selenium WebDriver. Supports multi-browser automation, element interaction, navigation, and web testing capabilities.5657 npm6MIT
- AlicenseAqualityCmaintenanceEnables AI agents and MCP clients to automate web browsers via Selenium WebDriver, supporting Chrome, Firefox, and Edge in headless or visible mode with tools for navigation, interaction, content extraction, screenshots, and scripting.219 npmMIT
- AlicenseNot gradedqualityDmaintenanceEmpowers AI agents to perform web browsing, automation, and scraping tasks with minimal supervision using natural language instructions and Selenium.9Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks like navigation, typing, clicking, and taking screenshots.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser for web automation tasks such as navigation, typing, clicking, and taking screenshots.-
TDQS
A3.6/5.0
Scored across 43 tools
Disambiguation4/5
Most tools target a distinct resource or action, and the browser_* vs devtools_* prefixes make intent clear. The main overlap is devtools_report, which aggregates what devtools_js_errors, devtools_console, and devtools_network_failed already expose, but their overview-vs-focused relationship is explained well enough.
Naming Consistency4/5
Names are snake_case and follow a readable prefix pattern: browser_<verb-like action> and devtools_<inspection/data>. Minor deviations like browser_status, browser_screenshot, and the noun-style devtools_* names keep it from being fully verb_noun, but the convention is predictable.
Tool Count2/5
43 tools is above the 25+ threshold and creates a heavy selection surface for an agent, even though the webdriver domain is broad. Some devtools_* getters could be consolidated, and the set would benefit from tighter scoping or splitting browser and devtools concerns.
Completeness4/5
The surface covers navigation, interaction, waiting, frames, dialogs, cookies/storage, screenshots, and detailed devtools diagnostics. Notable gaps like multi-tab/window management and drag-and-drop are missing, but most core webdriver workflows are fully supported.
Maintenance
ActivityActive
ResponsivenessResponsive