zen
Related Servers
Alternatives to zen
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to control Firefox by listing and managing tabs, navigating, taking screenshots, reading pages, clicking and typing, and inspecting console and network activity through a local bridge.32 npmMIT
- 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
- 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 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.4 npmMIT
- 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
TDQS
Scored across 24 tools
Most tools target a clearly distinct action (click, hover, type, form_input, key) and the descriptions explicitly separate the close pairs (type vs. form_input vs. key; read_page vs. get_page_text vs. find). A few boundaries are softer — navigate vs. tab_create-at-URL, and annotate vs. show_card both draw things on the page — but the descriptions resolve these well enough that misselection is unlikely.
Two conventions coexist: around half the tools use verb_noun snake_case (form_input, clear_annotations, read_page, show_card, wait_for, resize_window) while others are bare single-word verbs (click, type, key, scroll, find, hover, navigate, screenshot, javascript). The tab tools also invert the order to noun_verb (tabs_list, tab_create, tab_close) instead of list_tabs/create_tab. It stays readable, but the pattern is genuinely mixed.
24 tools sits in the heavy-but-defensible band: browser automation legitimately needs navigation, tab management, page reading, input, and debugging surfaces. Still, several are niche (resize_window, close_cards, clear_annotations, network_requests) and push the set past the point where an agent can hold the whole surface in mind cheaply.
Coverage of the browsing lifecycle is strong: tab create/list/close, navigation, structured and text reading, search, input, screenshots, JS execution, console and network inspection, plus waiting and window sizing. Minor gaps remain — no explicit tab activation/focus switch for a specific existing tab, no drag-and-drop, no cookie/storage or download handling — though most of these can be reached through javascript.