FoxMCP
Related Servers
Alternatives to FoxMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server paired with a Firefox extension that enables LLM clients to control the user's browser, supporting tab management, history search, and content reading.20 npm341MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server for Firefox that gives AI agents full control over the browser via a Unix socket, enabling automation of tabs, pages, cookies, and more without exposing any network ports.36 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes Firefox browser automation capabilities through the Model Context Protocol, enabling AI assistants to control web browsers for navigation, interaction, and data collection tasks.4BSD 3-Clause
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to automate a privacy-focused Firefox-based browser through MCP, with session and profile management, navigation, interaction, extraction, screenshots, JavaScript execution, tabs, downloads, and permission/URL validation.MIT
- 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
- AlicenseBqualityBmaintenanceLet AI agents use the Firefox, Zen, or LibreWolf browser you already have open, with your logins, cookies, and extensions intact. No Playwright, Chromium, or WebDriver. Agents work in background tabs while you keep browsing: read pages, click, fill forms, take screenshots, and capture network traffic. A WebExtension plus a local bridge lets several agents share one browser.27383 PyPI32MIT
TDQS
Scored across 46 tools
Tools are grouped by browser resource and mostly target clear, distinct operations. The main overlaps are profiles_list vs debug_websocket_status for connection/profile discovery and content_execute_script vs content_execute_predefined for JavaScript execution, but the descriptions make these separable with care.
Most domains use resource_action names such as tabs_list, bookmarks_create, navigation_reload, and containers_update. However, the window cluster reverses the convention to verb_noun names like list_windows, get_window, and create_window, so the overall set mixes two readable but inconsistent patterns.
At 46 tools, the surface is very large and exceeds the typical well-scoped range. The breadth reflects full browser automation, but several granular tab, window, and bookmark operations could be consolidated to reduce selection burden.
Coverage spans profiles, windows, tabs and tab groups, bookmarks, history, containers, navigation, content access, screenshots, and request capture, which is substantial for a browser automation server. Minor gaps exist around pinning/unpinning tabs and explicit bookmark-folder deletion, but core lifecycle workflows are present.