camoufox

Camoufox Browser Automation

Camoufox is a privacy-focused Firefox exposed through the camoufox-mcp-server MCP server. Reach for it when a plain HTTP fetch is not enough: JavaScript-rendered pages, bot walls, forms, multi-step flows, screenshots, or anything that benefits from a realistic browser fingerprint.

Every tool launches or reuses a real browser, so each call costs time and tokens. The whole skill is about getting the answer in the fewest, narrowest calls. Two habits do most of the work:

1. Pick the narrowest tool for the question (see Choosing a Tool). A page's link list, headings, or one text match is far cheaper than its full rendered text.
2. Bound every call. Set maxChars, selector, or outputMode: "metadata" so a giant page can't blow up your context.

This skill does not start the server. Confirm an MCP server named camoufox is available first. The installable plugin ships this config with unsafe browser options enabled so hard-site tuning can use firefox_user_prefs, args, and exclude_addons:

{
  "mcpServers": {
    "camoufox": {
      "command": "npx",
      "args": ["-y", "camoufox-mcp-server@latest"],
      "env": { "CAMOUFOX_MCP_ALLOW_UNSAFE_OPTIONS": "1" }
    }
  }
}

Bare npx -y camoufox-mcp-server@latest remains safe by default unless the host config adds that env var.

On a fresh machine, install the Camoufox binary once. From a repository checkout, run npm run fetch:camoufox. Global installs of 2.6.0 expose camoufox-mcp-fetch and camoufox-mcp-doctor. After release 2.6.0 is published, npx installs can use npx --yes --package [email protected] camoufox-mcp-fetch (replace the last command with camoufox-mcp-doctor for diagnostics). Use the same environment as the MCP server. Avoid camoufox-js fetch: its updater can select a build that bypasses WebSocket interception. Status and launch preflight inspect the cache without downloading.

Bring the Server Up (operator / local checkout)