orchords-web-pilot
OfficialRelated Servers
Alternatives to orchords-web-pilot
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceExposes a remote browser as MCP tools via Playwright, enabling AI agents to navigate and interact with web pages through DOM snapshots, clicks, typing, and form operations.409 npm12Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.2Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP clients to automate a real Chrome browser via Playwright, supporting session sharing and tools for navigation, clicking, typing, and more.112MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.3,667 npm57-
- FlicenseBqualityDmaintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.101-
- FlicenseNot gradedqualityDmaintenanceExposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.-
TDQS
Scored across 15 tools
Each browser_ tool serves a distinct, well-defined action—navigation, snapshot, click, type, fill, press, hover, drag, select, screenshot, evaluate, wait, console, network, and captcha solving. Even the text-entry tools (type vs. fill) are clearly differentiated by their descriptions, eliminating ambiguity.
All tools consistently use the 'browser_' prefix followed by a descriptive verb (or verb+noun) in lowercase snake_case, such as browser_navigate, browser_screenshot, browser_captcha_solve. This uniform pattern makes the tool names predictable and easy to learn.
With 15 tools, the set is appropriately scoped for a comprehensive browser automation server. Each tool covers a specific aspect of web interaction without being redundant or overwhelming, staying within the ideal range for a focused purpose.
The tool surface covers the full lifecycle of browser interactions: navigation, inspection, element actions, waiting, screenshotting, JavaScript execution, and special handling like captchas. Minor gaps like tab/multi-page management or dialog handling exist, but they are non-essential for most web-pilot tasks.