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
- FlicenseNot gradedqualityBmaintenanceEnables Claude Code to control a real browser using AI for web scraping, competitive intelligence, and UX auditing through the MCP protocol.-
- AlicenseAqualityCmaintenanceEnables browser automation and web data extraction through MCP tools, including Markdown reading, screenshots, structured data extraction, page inspection, and allowlisted site crawling.10447 npmMIT
- AlicenseAqualityAmaintenanceEnables browser automation for coding agents via MCP, allowing them to open pages, search, extract data, click, type, and complete multi-step tasks with fast single-round-trip decisions.14142 PyPI4MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities. This agent enables Claude to interact with web content, manipulate DOM elements, execute JavaScript, and perform API requests.1318 npm41TypeScriptMozilla Public 2.0
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.