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.3227 npm156MIT
- 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.145 npm6MIT

agentify-desktopofficial
AlicenseNot gradedqualityCmaintenanceMCP 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.21 npm567Mozilla Public 2.0- AlicenseNot gradedqualityCmaintenanceA 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 gradedqualityCmaintenanceAn MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.312MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that gives Claude Code a real browser to navigate, click, type, screenshot, and inspect pages via accessibility snapshots. It also runs multi-step test scenarios with assertions, session recording, visual regression, and console/network monitoring from the terminal.106 npmMIT
TDQS
Scored across 11 tools
Most tools have clearly distinct browser-automation purposes, especially tab management and navigation versus interaction. The main overlap is read_page vs get_text, since both extract page content, but the descriptions distinguish interactive outline/refs from readable main text.
All names use snake_case and are generally readable and predictable. There are minor deviations: several tools are single verbs (type, click, navigate, scroll) and screenshot is a noun, so it is not a uniform verb_noun convention.
The 11 tools are well-scoped for a browser automation server. Each covers a distinct common browser operation, and the count is neither bloated nor too thin.
Core browser workflows are covered: read page, get text, click, type, scroll, screenshot, navigate, and tab management. Some useful operations are missing, such as hover, general key presses beyond typing/Enter, waiting for selectors, and retrieving the current URL, but agents can work around many of these.