A
licenseNot graded
qualityD
maintenanceA browser automation MCP server with stealth mode, profile management, and multi-browser support, enabling LLMs to control browsers for tasks like navigation, data extraction, and form filling.
5 npm
1
MIT
agent-browser-mcp
by minhlucvan
Related Servers
Alternatives to agent-browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables LLM applications to control web browsers via Browserbase, supporting features like web navigation, screenshots, cookie management, and persistent contexts.172,030 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides browser automation using Playwright, enabling LLMs to interact with web pages through structured accessibility snapshots.ISC
- AlicenseAqualityCmaintenanceMCP server providing browser automation for AI agents, enabling actions like clicking and typing, structured data extraction, content validation, multi-step task execution, and memory enrichment from web pages.8487 npmMIT
- AlicenseAqualityCmaintenanceMCP server for browser automation that lets LLMs interact with web pages through structured accessibility snapshots, bypassing the need for screenshots.2310,188,231 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceA browser-automation MCP server that lets a calling LLM state one desired outcome at a time while a separate model decides the element, action, value, and completion status per round, enabling navigation, form filling, verification questions, page reading, and invocation of WebMCP tools a site registers.889 npmMIT
TDQS
B3.3/5.0
Scored across 32 tools
Disambiguation4/5
Most tools have distinct purposes, though browser_fill and browser_type both handle text input and could be confused without careful reading. Overall, actions and queries are clearly separated.
Naming Consistency5/5
All tools share the browser_ prefix and use a consistent verb-based pattern (e.g., browser_navigate, browser_get_text, browser_set_cookie). This makes the tool set predictable and easy to navigate.
Tool Count2/5
At 32 tools, this exceeds the threshold for well-scoped sets. While each tool has a purpose, the sheer number feels heavy and some utilities (e.g., separate is_visible/is_enabled/is_checked) could be consolidated.
Completeness4/5
The tool set covers core browser automation workflows—navigation, interaction, state extraction, cookies, and diagnostics. Missing elements like tab/window management and file uploads are notable but not critical for most tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues