zen-browser
Related Servers
Alternatives to zen-browser
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables Claude Code to control a Firefox-based browser by listing and opening tabs, reading pages, clicking, typing, filling forms, taking screenshots, running JavaScript, and inspecting console and network activity.24MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to drive a Firefox-based browser through WebDriver BiDi with tools for opening and navigating tabs, reading pages, clicking and typing, filling forms, running JavaScript, inspecting console and network logs, handling dialogs, uploading files, and recording GIFs. Interactions use real trusted input events and an isolated page runtime so sites behave as they do for a person.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to drive a local Firefox browser: opening and managing tabs, navigating, reading page structure and text, clicking, typing, filling forms, running JavaScript, taking screenshots, and inspecting console messages and network requests. Everything runs over a local Unix socket with no network traffic, and actions are restricted to tabs explicitly placed under Claude's control.4 npmGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to control Firefox through tools for tabs, navigation, clicks, typing, scrolling, screenshots, page reading, forms, JavaScript, and console/network logs.MIT
- AlicenseBqualityCmaintenanceLets Claude Code attach to a running, signed-in Firefox over WebDriver BiDi to control tabs, navigate, screenshot, read pages, click, type, fill forms, evaluate JavaScript, and inspect console/network activity.22MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to control the user's real Firefox browser through a local MCP server, with tools for tabs, navigation, page reading, clicking, typing, forms, screenshots, and file uploads under per-site consent.MIT
TDQS
Scored across 15 tools
Most tools target clearly distinct actions: tab lifecycle (tabs_*), navigation, page reading, element finding, form input, JS eval, console/network reading. The main overlaps are the standalone screenshot tool versus computer's built-in 'screenshot'/'zoom' actions, and read_page vs get_page_text vs find, which require reading descriptions to separate. These are minor and descriptions do disambiguate, but an agent could still occasionally reach for the wrong page-reading tool.
The tabs_* group is consistent but uses noun_verb order (tabs_create, tabs_close) while other tools use verb_noun (get_page_text, read_page, resize_window) or bare nouns/verbs (screenshot, navigate, computer, javascript, find). It's readable and mostly self-explanatory, but two conflicting conventions coexist with no unifying scheme.
15 tools is well within a healthy range for a browser-automation server, and each tool maps to a meaningful capability (tab management, interaction, inspection, diagnostics). Nothing feels redundant enough to cut, and no obvious gap-forcing consolidation is needed.
The surface covers the full browser workflow: tab lifecycle, navigation with history, screenshots, DOM reading, element search, form filling, JS execution, console and network diagnostics, and window resizing. Minor gaps exist—no drag-and-drop action in computer, no cookie/localStorage or download management, and no explicit reload—but agents can work around these via javascript or navigate.