Browser MCP
Related Servers
Alternatives to Browser MCP
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools. Provides browser automation, performance analysis, debugging capabilities, and network request monitoring.3,202,397 npm52,668Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for browser automation that lets LLMs interact with web pages through structured accessibility snapshots, bypassing the need for screenshots.6237,529,920 npmApache 2.0
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to navigate and interact with web pages through compressed semantic graphs, using element IDs and coordinates for clicking, typing, selecting, scrolling, and screenshots without raw HTML or CSS selectors.39 npm1MIT
- AlicenseAqualityCmaintenanceConverts raw HTML into structured, AI-readable page maps with 97% token reduction, enabling agents to read, click, type, and navigate any web page.91336AGPL 3.0
- AlicenseCqualityAmaintenanceEnables AI agents to automate real Chrome via a structured Semantic Action Graph, without screenshots, CDP, or bot detection. It supports clicks, form filling, navigation, and state diffs on strict-CSP sites and modern SPAs.315MIT
- AlicenseAqualityDmaintenanceEnables AI agents to understand web page structure and content through structured data extraction and element discovery using Playwright, eliminating the need for screenshots.47 npmMIT
- AlicenseNot gradedqualityAmaintenanceReachability-filtered browser perception and actions for AI agents. Filters snapshots to elements a user could actually reach (removes modal-occluded, closed-drawer, off-screen and inert elements), with ref-stable snapshots and state diffs.1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to perceive and interact with web interfaces by extracting a unified UI Scene Graph from live URLs, providing tools for navigation, element detection, visual analysis, and state tracking.1-
TDQS
Scored across 26 tools
Each tool has a clearly distinct purpose, from navigation (navigate, go_back) to element interaction (click, hover, drag) to form handling (get_form, type). There is no overlap between tools; even similar operations like scroll and wheel are differentiated by mechanism.
Tool names follow a consistent verb_noun pattern, using snake_case for multi-word names (e.g., close_page, list_pages, scroll_to). Single-word verbs (click, drag, hover) are also consistent. No mixing of conventions.
With 26 tools covering navigation, interaction, form handling, network inspection, and canvas analysis, the count is slightly high but justified for a comprehensive browser automation server. Each tool serves a specific need, though a few might be consolidated.
The tool set covers most common browser automation tasks, but notable gaps exist: no explicit wait_for_element or wait_for_navigation, no JavaScript execution, and no cookie management. These omissions may require workarounds for certain scenarios.