An MCP (Model Context Protocol) server that provides browser automation capabilities using Camoufox, a privacy-focused Firefox fork with advanced anti-detection features.
Quick Install
MCP server for browser automation using Camoufox - a privacy-focused Firefox fork with advanced anti-detection features
2026-11-15
Sterne
—
Tools
—
Uptime
—
Use the published npm package unless you are developing this repository locally.
Tell your LLM
Install camoufox-mcp and the skill using this URL: https://raw.githubusercontent.com/whit3rabbit/camoufox-mcp/refs/heads/main/llms.txt
Claude Code CLI
claude mcp add camoufox -- npx -y camoufox-mcp-server@latest
For a shared project-scoped Claude Code config:
claude mcp add --scope project camoufox -- npx -y camoufox-mcp-server@latest
Codex stores MCP servers in ~/.codex/config.toml by default. Verify with /mcp inside Codex.
Agent Skill and Plugin Bundle
Use these when you want the camoufox skill plus the packaged MCP server config. If you only need the MCP server, use the Claude Code or Codex MCP commands above. Bare npx -y camoufox-mcp-server@latest remains safe by default. The packaged plugin bundle enables CAMOUFOX_MCP_ALLOW_UNSAFE_OPTIONS=1 so the skill can use firefox_user_prefs, args, and exclude_addons for hard-site tuning.
OpenClaw
Register the MCP server directly. This works today with no registry publish (--arg
is singular and repeatable; the --env flag enables the unsafe-option tuning):
Hermes TTY Gotcha:hermes mcp add interactively prompts "Enable all 17 tools? [Y/n/select]". On a non-TTY (piped/scripted inputs), the default response is "n" (canceled). Pipe Y\n as shown above to enable tools automatically.
Do not run hermes plugins install … for this repo. Hermes plugins are Python
packages with a root plugin.yaml; this repo has neither, so it clones but is rejected
as "not a valid plugin." Use the two commands above.
Hermes treats --args as plain argv tokens and it must be the last option. Do not pass a
JSON array string there. In ~/.hermes/config.yaml, env must be a mapping
(KEY: "value"), not a list. Verify with:
hermes mcp list
hermes mcp test camoufox
First browse on a fresh machine needs the browser binary once; download and storage
requirements vary by platform and build. If a call
reports it is missing, run the pinned fetch script and retry: npm run fetch:camoufox
(repo checkout). After release 2.6.0 is published, npx installs can use
npx --yes --package [email protected] camoufox-mcp-fetch.
Global installs of 2.6.0 provide camoufox-mcp-fetch and camoufox-mcp-doctor.
Do not use camoufox-js fetch: its release selection can install a build that
bypasses page WebSocket interception.
Restart Hermes from a separate terminal after changing MCP config. Hermes namespaces MCP
tools as mcp_camoufox_<tool> (single underscore, e.g. mcp_camoufox_browse,
mcp_camoufox_camoufox_status; some setups show the double-underscore form
mcp__camoufox__browse) — use whatever your tool list shows, and confirm
mcp_camoufox_camoufox_status reports unsafeOptionsAllowed: true. browser_navigate is
Hermes' own built-in browser tool, not Camoufox.
Local and private hosts are blocked by default. Source builds from main support an explicit hostname allowlist. npm/npx installs gain this setting in the next tagged release.
Add an env entry to your MCP server configuration:
Restart the MCP server, then check camoufox_status.networkSecurity.allowedPrivateHosts. Configure DNS or hosts entries in the same container or VM as the server and browser. Corporate and custom DNS names also work when explicitly listed.
For eligible private hosts, the MCP error text includes the exact allowlist setting and restart instruction. Read the full error and append the required hostname to any existing list.
Entries are exact hostnames, without IP literals, wildcards, URLs, or ports. This is a server environment setting, separate from browse parameters and CAMOUFOX_MCP_ALLOW_UNSAFE_OPTIONS. Metadata, link-local, and reserved addresses remain blocked. See local development policy for scope.
Try Camoufox
Once configured, ask your assistant for browser work in plain language:
Use Camoufox to browse https://example.com and return metadata only.
Use Camoufox to inspect the interactive elements on https://example.com.
Use Camoufox to open https://example.com, take a screenshot, and summarize the visible page.
Use Camoufox to browse https://developer.mozilla.org with images blocked and WebRTC blocked.
Features
Advanced anti-detection: rotating OS fingerprints, realistic cursor movements, and browser fingerprint spoofing.
Session tools: short-lived isolated browser sessions with challenge pause/resume support.
Requirements
Published default runtime: Node.js 22.0 or higher
Repository builds and compatibility mode: Node.js 22.15 or higher, with npm install --include=optional
Python 3.x for running tests
Versioning
The default pins are camoufox-js 0.12.0, playwright-core 1.59.0, and Camoufox 152.0.4-beta.28. Keep playwright-core as a direct pinned dependency: npm overrides alone do not pin it for npx or global installs. Run npm run doctor to verify the selected build and a real browser launch.
Camoufox 156.0.1-beta.33 is available through opt-in compatibility mode. It restores page and iframe WebSocket interception by disabling the newer browser's world isolation, reducing stealth compared with its upstream defaults. The beta.28 default predates that isolation change. Worker WebSockets evade interception in both modes, so untrusted browsing needs network egress controls. See browser compatibility setup and evidence before enabling it.
Environment variable
Default
Effect
CAMOUFOX_MCP_BROWSER_COMPATIBILITY
Unset
Set to 1 during installation and startup to select beta.33 with reduced stealth.
CAMOUFOX_INSTALL_DIR
OS cache, separate camoufox-compatibility cache when opted in
Override the browser directory; use the same value during installation and startup.
Use npm run fetch:camoufox for tagged downloads with SHA-256 checks. The shared browser manifest pins both modes. Avoid camoufox-js fetch, whose release selection can install a build that bypasses WebSocket interception.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Camoufox?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Camoufox einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Camoufox?
Camoufox läuft lokal über stdio.
Wann wurde Camoufox zuletzt geprüft?
Zuletzt geprüft: 2026-11-15. MCP server for browser automation using Camoufox - a privacy-focused Firefox fork with advanced anti-detection features
