A
licenseNot graded
qualityC
maintenanceMCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
9
MIT
mcp-browser-parallel
by Mokecy
Related Servers
Alternatives to mcp-browser-parallel
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to control multiple independent browser instances in parallel with process-level isolation, supporting any backend MCP server for browser automation.271,02017MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.1492MIT
- AlicenseBqualityDmaintenanceA concurrent browser MCP server that supports multiple parallel browser instances206411Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server for QA and test automation that provides runtime switching between multiple browser profiles (Chromium, Firefox, WebKit) without restart, enabling cross-browser regression testing, multi-account testing, localization QA, and more.7MIT
- AlicenseAqualityAmaintenanceA local, open-source MCP server that enables AI clients to control multiple isolated Chromium browser sessions concurrently, with explicit session and page addressing and independent state.35204Apache 2.0
TDQS
B3.4/5.0
Scored across 36 tools
Disambiguation5/5
Each tool has a clear, distinct purpose. Even similar actions like click vs mouse_click_xy are differentiated by targeting element vs coordinates. Fill, fill_form, and type are distinct in scope and behavior.
Naming Consistency5/5
All tools follow a consistent category_verb pattern in snake_case. Prefixes like browser_, instance_, page_ clearly indicate the scope. Multi-word verbs are used consistently.
Tool Count3/5
With 36 tools, the set is larger than typical recommendations (25+). However, the browser automation domain inherently requires many distinct actions. The count is borderline but justified by the comprehensive coverage.
Completeness5/5
The tool set covers the full lifecycle of browser interactions: connection, instance management, navigation, all major user actions, state inspection (snapshot, console, network), debugging (tracing), and output (screenshot, PDF). No obvious gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues