Camoufox MCP Server
Related Servers
Alternatives to Camoufox MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides stealthy browser automation capabilities using a custom Firefox build designed for anti-detection. It enables users to navigate pages, interact with elements, and manage persistent browser sessions through natural language.15 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLMs to launch a fingerprint-randomized browser, navigate, click, type, read the DOM, and take screenshots through a patched Firefox engine.MIT
- FlicenseNot gradedqualityDmaintenanceProvides stealth web browsing using dual browser engines (Chromium and Firefox) with automatic bot-detection bypass, enabling AI agents to browse, interact, and extract content from websites without being blocked.1-
- AlicenseBqualityCmaintenanceEnables LLMs to drive a stealthy, fingerprint-spoofed Firefox browser via MCP tools, supporting navigation, interaction, extraction, and multi-session management.8441 PyPI1MIT
- AlicenseAqualityDmaintenanceEnables browser automation with anti-detection features, including navigation, interaction, form filling, and session management.2226 PyPI10MIT
- FlicenseNot gradedqualityBmaintenanceProvides 29 stealth-browsing tools for AI agents, enabling undetected web automation and scraping through a patched Chromium engine.629-
TDQS
Scored across 17 tools
Many tools share the 'browse' prefix and differ only in output focus, such as browse, browse_snapshot, browse_outline, and browse_forms. Session-based equivalents like browse_session_navigate and browse_session_snapshot mirror one-shot tools, creating ambiguity about which to use. This overlap makes tool selection challenging.
The server uses snake_case, but the prefix pattern is inconsistent: bare 'browse', 'browse_*', 'browse_session_*', and 'camoufox_status'. While the verb 'browse' is common, the mix of noun and verb forms and the odd 'camoufox_status' break predictability. Overall readable but not uniform.
At 17 tools, the count is on the higher end of the appropriate range for a browser automation server. The breadth covers one-shot browsing, session management, and diagnostics, so it's not excessive, but it's borderline heavy. A few tools could be merged without losing functionality.
The server covers navigation, content extraction, screenshotting, diagnostics, and session lifecycle. It lacks dedicated form-filling or cookie tools, but browse_sequence and browse_session_action provide generic action execution. Core browsing workflows are supported, with only minor gaps.