Edge DevTools MCP
Related Servers
Alternatives to Edge DevTools MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to drive a running Microsoft Edge browser over the Chrome DevTools Protocol, exposing 16 tools for navigation, clicking, typing, screenshots, page-content reading, and tab management. Runs in stdio mode for per-client processes or as a shared HTTP endpoint so multiple agents can operate the same browser session.16MIT
- AlicenseAqualityCmaintenanceEnables LLM agents to launch or attach to a Microsoft Edge session and drive it through a four-tiered tool set spanning navigation, clicking, typing, and token-efficient accessibility-tree inspection. Also exposes raw Chrome DevTools Protocol calls for network interception, cookie manipulation, console and performance telemetry, and device emulation.202MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to launch and control a real Edge/Chrome browser over CDP, navigating pages, inspecting elements, clicking and typing, extracting structured data, and reading network/console activity or taking screenshots.MIT
- FlicenseNot gradedqualityAmaintenanceEnables remote agents to control a local Chrome/Edge browser via MCP, supporting navigation, snapshots, clicks, typing, screenshots, and script execution.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Codex, Claude Code, and Cursor to connect to Microsoft Edge through automatic browser discovery and the official Chrome DevTools MCP server, preserving cookies, sessions, and extensions.11 npmMIT
TDQS
Scored across 14 tools
Most tools map to a clear action (navigate, click, type, screenshot), but the element-inspection cluster overlaps heavily: edge_get_element, edge_dom_query, and edge_get_attributes all read as ways to fetch element/DOM information, and edge_connect / edge_enable_devtools / edge_get_targets all sit in the session-setup space. Descriptions help somewhat but an agent could easily misselect among the inspection tools.
All names use a consistent edge_ prefix with snake_case verb_noun structure (edge_click_element, edge_get_page_content, edge_type_text). Minor deviations: edge_screenshot is noun-only with no verb, and edge_wait_for_selector inserts a preposition, but the pattern remains predictable.
14 tools is well within a reasonable scope for browser automation and each major capability (connect, navigate, interact, inspect) has representation. A few slots feel redundant, notably edge_enable_devtools alongside edge_connect, and the three overlapping inspection tools.
Core flows are covered — connection, navigation, JS evaluation, screenshots, click/type, waiting, and DOM inspection. However, key DevTools-domain operations are missing: no keyboard key presses, hover/scroll or select-option handling, and critically no console log or network request retrieval, which are central to a DevTools server's stated purpose.