browser-mcp
Related Servers
Alternatives to browser-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server that wraps agent-browser to let LLMs control a real browser, providing tools for navigation, interaction, reading page content, accessibility snapshots, screenshots, and session management.1-
- AlicenseAqualityCmaintenanceBrowser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.2217 npmMIT
- AlicenseNot gradedqualityBmaintenanceLocal browser MCP server that lets AI assistants control a real desktop browser via tools like navigate, snapshot, and search_web.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that lets AI agents drive the locally installed Chrome or Edge, opening pages, taking compact accessibility-tree snapshots with @e references, and clicking, typing, scrolling, or capturing screenshots. It also exposes multi-account and cross-channel tab switching, tab sync rules, and ad-block/perf statistics.MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives AI agents token-efficient, structured access to web pages, returning compact page orientations and targeted element queries instead of full accessibility-tree dumps, plus browser interaction, monitoring, and session management tools.4 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server providing AI agents with a stealth Chromium browser that uses hybrid accessibility-object-model and set-of-mark vision for token-lean snapshots and reliable action via ref ids.1397 npm1Apache 2.0
TDQS
Scored across 15 tools
Each tool has a unique and clear purpose: navigate, click, type, scroll, press keys, snapshot, console, images, network logs, intercept, export steps, list steps, and vision. No two tools overlap in function.
All tools follow the consistent pattern 'browser_verb[_noun]' in snake_case (e.g., browser_navigate, browser_get_network_logs). No mixing of conventions.
15 tools cover the core browser automation domain without being excessive. The count is well-scoped for navigation, interaction, debugging, and recording.
The tool surface covers navigation, DOM interaction, snapshot, screenshot, console, network logging, request interception, and step recording/exporting. No obvious gaps for standard browser automation tasks.