zenpilot
Related Servers
Alternatives to zenpilot
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceAn MCP server that gives Claude Code real browser control for web automation, testing, and screenshots.3246 npm158MIT
- AlicenseAqualityCmaintenanceA lean, LLM-first browser automation MCP server that gives Claude (or any MCP client) a real Chromium browser to navigate, interact with, and debug web apps.147 npm6MIT

agentify-desktopofficial
AlicenseNot gradedqualityDmaintenanceMCP server that enables AI tools to control local browser sessions for ChatGPT, Claude, and other AI services, supporting querying, navigation, file uploads, and artifact management.575Mozilla Public 2.0- AlicenseNot gradedqualityDmaintenanceA standalone MCP server that lets Claude Code, opencode, and other MCP clients control your real browser via the QoderWork browser connector extension, preserving login state and providing tools for navigation, clicking, typing, screenshots, and more.ISC
- AlicenseNot gradedqualityDmaintenanceAn MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.316MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets Claude (or any MCP client) drive the user's own browser — with their existing sign-ins — in a separate window of its own, so pages can be opened, read, and acted on without stealing focus or interrupting the user's work.184 npm1MIT
TDQS
Scored across 26 tools
Each tool targets a distinct browser-automation operation: tab management, page reading, interaction, network inspection, screenshots, dialogs, and viewport resizing. The apparent overlaps like read_page/find/get_text and read_network_requests/network_request/har_export are clearly differentiated by scope and output.
Tool names consistently use lower_snake_case and are mostly readable action-oriented names. There are minor deviations such as single-word verbs (click, type, select) and noun-first names (screenshot, har_export, network_request), but no jarring mixed conventions.
At 26 tools, the surface is slightly above the typical ideal range and feels heavy, but the broad browser-automation scope justifies most tools. Each capability is distinct enough that the count is reasonable rather than bloated.
The set covers core browser automation well: tabs, navigation, reading, clicking/typing/selecting, waiting, dialogs, screenshots, network inspection, HAR export, and request mocking. Gaps remain around drag-and-drop, iframe content, browser history/reload shortcuts, cookies/storage, and direct JS evaluation, but these are mostly edge or advanced operations.