usable-browser-agent-free
Related Servers
Alternatives to usable-browser-agent-free
No user-submitted related servers found.
Related Servers
- 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.1358 npm1Apache 2.0
- AlicenseAqualityAmaintenanceMCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.251Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI agents secure, consent-based access to a single browser tab, supporting read-only snapshots, element interaction with per-action approval, and frozen multi-step plans, all audited.MIT
- AlicenseNot gradedqualityDmaintenanceSecurity-hardened MCP server that gives AI assistants full control over your real browser session, supporting 36 tools for navigation, data extraction, monitoring, and more.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that gives AI agents a durable identity, persistent browser, memory, and coordination tools, enabling them to maintain state across sessions and act on the live web.3MIT
- AlicenseAqualityBmaintenanceBrowser 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.2235 npmMIT
TDQS
Scored across 53 tools
Most tools target distinct actions and resources with detailed descriptions, and overlapping pairs like browser_type vs browser_paste vs browser_os_type are clearly differentiated. A few similar-sounding tools (browser_status vs browser_info, browser_snapshot vs browser_screenshot) still require careful reading, so it is not perfect.
All tools share the browser_ prefix and most follow a clear verb_noun pattern (browser_list_tabs, browser_close_tab, browser_upload_file). There are minor deviations like noun-only names (browser_status, browser_snapshot) and noun-verb ordering (browser_workflow_recall), but the overall pattern remains predictable.
53 tools is far beyond the typical well-scoped 3-15 range and exceeds the 50+ threshold for an extreme mismatch. Even for a broad browser-automation domain, the surface is bloated with many variants (OS-level clicks, clipboard image handling, workflow memory) that could likely be consolidated.
The tool set covers the full browser lifecycle: tabs, navigation, interaction, forms, secrets, clipboard, downloads/uploads, dialogs, screenshots, network inspection, and OS-level fallbacks. Minor gaps like cookie management and console-log inspection exist but can be worked around via browser_eval or browser_network_log.