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.1,737,496 npm53,859Apache 2.0
- AlicenseAqualityCmaintenanceMCP server for browser automation that lets LLMs interact with web pages through structured accessibility snapshots, bypassing the need for screenshots.233,465,430 npmApache 2.0
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to navigate, inspect, and interact with web pages through a compact structured representation, returning lightweight page orientations and targeted element queries instead of full accessibility-tree dumps.4 npm-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to browse, navigate, and interact with web pages through structured, token-efficient page representations — returning compact orientations and targeted element queries instead of full accessibility-tree dumps.4 npm-
- 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.16 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to browse and interact with web pages through a typed, structured representation — receiving a compact orientation on arrival, targeted queries for specific elements, and full detail only when explicitly requested, instead of a bulky accessibility-tree dump. Supports navigation, clicking, typing, form filling, screenshots, tabs, console/network monitoring, and selectable tool profiles to cut per-call definition overhead.4 npm-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to browse and interact with web pages through compact, typed structural representations — landmarks, headings, interactive elements, and forms — served in three controllable detail levels instead of full accessibility-tree dumps. Agents can navigate, query for specific elements, fill forms, manage tabs and cookies, capture screenshots, and run audits while paying a fraction of the token cost.4 npm-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to browse, query, and interact with web pages through structured, token-efficient representations instead of full accessibility-tree dumps, returning compact page orientations and targeted element details only when requested. Supports navigation, observation, forms, screenshots, session and tab management, and development auditing.4 npm-
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.