Kitsune
Related Servers
Alternatives to Kitsune
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to automate and control a real Firefox instance over WebDriver BiDi through 177 browser_* tools spanning web pages, tabs, windows, bookmarks and history, settings, extensions, DevTools, translation, certificates, and more across 17 domains.178MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control existing Chrome and Firefox browser sessions locally, including tab management, navigation, form filling, screenshots, and persistent scripts, without remote relays or debugging ports.23 npm-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to operate a real, logged-in Firefox session through an extension, including tab and history management, page reading, screenshots, and clicking, typing, or scrolling on domains the user approves.23 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control the user's real Chrome or Firefox tabs, with their existing logins, to read pages, click, type, fill forms, take screenshots, inspect network traffic and run JavaScript. It works through a paired browser extension over a local WebSocket connection, so automation happens in the browser the user is actually looking at, including shadow DOM, cross-origin iframes, dialogs and single-page apps.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to drive a user-launched Firefox instance via its native Marionette protocol, providing precise DOM actuation like clicking, typing, uploading files, taking screenshots, and evaluating JavaScript.1820 npm1GPL 2.0
- AlicenseNot gradedqualityAmaintenanceExposes a 47-tool browser automation surface to MCP clients, enabling AI agents to navigate, interact with, observe, and extract content from web pages across multi-tab sessions. Runs on Camoufox-based anti-detection behavior so agents can automate sites that block conventional headless browsers, with session persistence, cookie import, and stdio or HTTP transport.549 npmMIT
TDQS
Scored across 27 tools
Most tools map cleanly to one browser action (click, hover, press_key, select_option, navigate, tabs), and the network_requests/network_request pair is explicitly documented as a two-step lookup. A few pairs have fuzzy boundaries: browser_type vs browser_fill_form, browser_drag vs browser_drop, and especially browser_evaluate vs browser_run_code_unsafe, where an agent must read carefully to pick the right one.
Every tool uses the same browser_ prefix and snake_case, which makes the set very predictable. The only minor deviation is that some names are verb-first (browser_click, browser_navigate_back) while others are noun/verb-phrase (browser_tabs, browser_snapshot, browser_network_requests, browser_console_messages).
At 27 tools this is on the heavy side and includes specialized operations (browser_emulate_media, browser_resize, browser_drop, browser_drag, browser_run_code_unsafe) that many agents will never need. For a full browser-automation surface the breadth is defensible, but the count is borderline rather than well-scoped.
Coverage is strong: navigation, tabs, forms, keyboard, dialogs, waits, snapshots, screenshots, console, network inspection, file upload, and drag/drop are all present. Gaps are minor but real: no forward-history navigation, no cookie/localStorage management, and no download handling.