Enhanced Browser MCP Server
Related Servers
Alternatives to Enhanced Browser MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA client-server browser automation solution that reduces HTML token usage by up to 90% through semantic snapshots, enabling complex web interactions without exhausting AI context windows.28206 npm15MIT
- AlicenseBqualityBmaintenanceA browser automation MCP server that enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or vision models.247,739,093 npmApache 2.0
- AlicenseAqualityAmaintenanceA token-efficient MCP server for Chrome browser automation that uses direct CDP and accessibility-tree-based references for stable element selection across DOM changes.25327 npm15MIT
- AlicenseNot gradedqualityDmaintenanceToken-efficient browser automation MCP server using Playwright, with getOutline and searchSnapshot to save ~95% tokens compared to full snapshots.22 npmMIT
- AlicenseNot gradedqualityDmaintenanceToken-optimized Playwright MCP server that reduces context window usage by 73.8% by grouping 22 tools into 6 semantic operations, enabling AI assistants to control browsers with minimal token overhead.20 npmMIT
- AlicenseBqualityDmaintenanceAn MCP server that provides browser automation capabilities, enabling LLMs to control a web browser for navigation, interaction, and data extraction.32439 npm14MIT
TDQS
Scored across 12 tools
Each tool targets a distinct browser action: navigation, history, interaction, state inspection, and waiting. Snapshot and screenshot are clearly separated (accessibility tree vs visual capture), and no two tools overlap in purpose.
All tools follow the browser_verb_noun pattern consistently, using lowercase and underscores. The verb clearly indicates the action (navigate, click, type, wait), making the set predictable and easy to navigate.
With 12 tools, the server is well-scoped for browser automation, covering essential actions without unnecessary bloat. This fits comfortably within the ideal range, and each tool earns its place.
The set covers core browser workflows: navigation, history, interaction, state reading, and waiting. Minor gaps exist (e.g., explicit scroll or page reload), but agents can work around them, making the surface reasonably complete for basic automation.