ZenLink MCP
Related Servers
Alternatives to ZenLink MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides browser automation capabilities through Claude Desktop and other MCP clients, enabling navigation, screenshot capture, content extraction, and interactive control.-
- AlicenseNot gradedqualityDmaintenanceEnables browser automation through the Claude Chrome Extension, allowing agents to navigate websites, fill forms, take screenshots, and debug web apps via standard MCP protocols.1MIT
- AlicenseAqualityAmaintenanceAn MCP server that enables Claude Desktop and Claude Code to drive a running Zen Browser over WebDriver BiDi, letting Claude list, open, switch, and close tabs, navigate pages, read page content, click, type, scroll, take screenshots, and extract text from a live browser session.26142 PyPI11MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigation, interaction, screenshots, accessibility snapshots, network and console monitoring, and automated end-to-end testing through MCP tools.106 npmMIT
- AlicenseBqualityBmaintenanceEnables Claude and other MCP clients to drive a stealth Chromium browser through 49 tools for navigation, page reading and extraction, interaction, session and fingerprint management, and debugging.55MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to control a real browser for navigation, interaction, screenshots, accessibility snapshots, and automated end-to-end testing through MCP tools.106 npmMIT
TDQS
Scored across 104 tools
Most tools have clearly distinct purposes, but there is some overlap among page content extraction tools (e.g., zen_page_text, zen_markdown, zen_readability) and command batching tools (zen_batch, zen_parallel, zen_broadcast). Detailed descriptions help differentiate them.
All tools follow the 'zen_' prefix with snake_case naming, predominantly using a verb_noun pattern (e.g., zen_click, zen_navigate, zen_wait_for_element). A few noun-only names (zen_tabs, zen_windows) fit the resource-listing pattern. Consistency is excellent.
With 104 tools, the count is very high for a browser automation server. Many tools are composite or highly specialized (e.g., zen_wp_html, zen_reload_extension), which adds complexity. A more streamlined set of ~30-50 core tools would improve coherence.
The tool set covers virtually all browser automation needs: navigation, element interaction, network capture, console logs, cookies, storage, tabs, windows, screenshots, and advanced features like keep-alive and sync barriers. No significant gaps are apparent.