CamoFox on Windows: Browser Download or MCP Setup?

On Windows, start with CamoFox Browser. Add CamoFox MCP only if you want an AI app to control that browser. The Browser's official portable ZIP runs the browser server without a separate system-wide Node.js installation. MCP is a second component: its documented npx setup still needs Node.js 18 or newer. Windows x64 runs the browser headlessly, so no browser window popping up is normal—not evidence that setup failed. This guide helps you choose the right download and verify each layer without guessing.

CamoFox Browser is the server that performs web actions; CamoFox MCP is a companion that makes those actions available to a compatible AI client. The underlying Camoufox engine is a different project. Auto-Bot.io publishes this editorial guide; the redf0x1 CamoFox repositories are the first-party download and documentation sources. If you want the broader product story rather than a Windows installation choice, see our CamoFox Browser introduction.

Which CamoFox download do you need?

Think of Browser as the engine room and MCP as an optional bridge to an AI assistant. The bridge cannot replace the engine room. Choose your path by what you want to do now:

Not sure? Do the Browser-only check first. You can add MCP later without treating the two repositories as alternative versions of the same download. If you only want an AI chat app to summarize a page you open yourself, you may not need browser automation at all. This article describes the official documented Windows x64 path as checked on September 26, 2026; it does not claim we installed the ZIP on a Windows machine.

1. Download and start Browser portable

1. Open the official CamoFox Browser v2.4.8 release and choose the asset named camofox-browser-2.4.8-windows-x64.zip. Confirm the repo owner is redf0x1, not a lookalike fork or the separate Camoufox engine. Check the release page for newer versions before downloading; the exact version here is a documented reference, not an automatic updater.
2. Extract the ZIP into a folder you can write to. The portable bundle keeps its data under data\home inside that folder, including profiles and engine cache. Do not run it from a read-only or temporary extraction preview.
3. Open PowerShell or Command Prompt in the extracted folder. Run the three commands below, one at a time. Their expected purpose is version → start → status; the literal status output may vary.

.\camofox.cmd --version
.\camofox.cmd server start --background
.\camofox.cmd server status

The first command displays the bundled CLI version. The second starts the local server, and the third checks its state. These commands and the Windows headless limitation come from the official Browser Windows instructions. You can stop the server with .\camofox.cmd server stop when you have finished. Do not expect a Firefox-style desktop window: the supported Windows portable contract is headless-only; headed and virtual-display modes are not supported there.

Staying on the Browser-only path? The official CLI examples also show an open → snapshot → close check. From the same extracted Windows folder, the bundled launcher accepts those actions:

.\camofox.cmd open https://example.com
.\camofox.cmd snapshot
.\camofox.cmd close

Look for “Example Domain” in the snapshot. This is a suggested check based on the documented CLI and portable launcher, not a Windows run that we performed.

If you only need direct browser automation, read the Browser CLI reference next. If you want an AI assistant to use this server, continue to MCP. The anti-detection design is not a guarantee that every site will permit or accept automation; follow the target site's rules and access rights.

2. Add MCP only for an AI client

The official MCP getting-started guide calls for three things: a running CamoFox Browser server, an MCP-compatible client, and Node.js 18 or newer when using npx to launch MCP. The Browser ZIP includes Node for its own launcher; that does not turn a Windows machine into one with a globally available npx. For this optional route, get Node.js from the official Node.js download page if it is not already installed; then open a new PowerShell window and check node --version (18 or higher) and npx --version (a version number). If a command is still not recognized, resolve that installation before downloading Browser again.

Which AI app? Use an MCP-compatible client you already have. For a single concrete desktop example, the vendor documents Claude Desktop below; this does not imply it is included in the Browser ZIP, free to use, or the only compatible client. Add the configuration using that client's documented method, then fully quit and reopen the client so it starts the MCP connector. The example below matches the official Claude Desktop configuration. Cursor uses the same mcpServers wrapper in that guide; VS Code uses a different format. Follow your client's instructions for where to save it.

{
  "mcpServers": {
    "camofox": {
      "command": "npx",
      "args": ["-y", "camofox-mcp@latest"],
      "env": { "CAMOFOX_URL": "http://localhost:9377" }
    }
  }
}

Use http://localhost:9377 when Browser is running on the same computer with its documented default address. If you changed its port or host, update CAMOFOX_URL to match. If you enabled browser-server API-key authentication, follow the vendor's authentication configuration; do not paste keys into an article, chat, or screenshot. Keep the server on a trusted local endpoint by default rather than exposing it publicly to make a connection error disappear.

Already have a working MCP client? The same guide has VS Code and Cursor examples. Our MCP basics guide explains the protocol, while the CamoFox MCP architecture article explores what agents can do after setup. Neither replaces the choice-and-check steps here.

3. Check the result, layer by layer

Do not jump directly to an AI prompt if the server is not running. The first-party verification flow separates connection problems from browser-action problems:

1. Browser: run .\camofox.cmd server status in the extracted folder. The documentation also suggests checking http://localhost:9377/health; a cold server can be healthy before any browser tab exists.
2. MCP: restart your chosen AI client after configuring it. Ask it to call server_status. If this cannot reach the server, check the Browser process, CAMOFOX_URL, your npx installation and—only if configured—matching API keys.
3. One harmless page: in the same client, paste this prompt: “Verify my CamoFox setup. Call server_status. If reachable, create a tab for https://example.com, call navigate_and_snapshot, and confirm the snapshot contains ‘Example Domain’. Close the test tab afterward. Report which step passed or failed.” A working status check alone does not prove page navigation works.

If the example page succeeds, a first real agent instruction can be: “Open a public page I provide, describe its visible links from a snapshot, click one link, and report what changed.” Review the resulting actions before using it on any other site. This is an example prompt, not an end-to-end run we performed or a promise that every page will work.

Session expectation: the documented MCP profile settings can preserve browser state such as cookies and local storage, but a saved profile is not a promise that a previously open tab will reappear or that MCP can adopt a tab opened by the Browser CLI. If you need separate sites or identities, plan separate sessions and test the behavior in your own client before relying on it. The vendor's session-sharing notes distinguish profiles, sessions and tabs.

Keep your first trial to a public example page; no login, proxy configuration or personal data is needed to decide whether the basic connection works.

If something looks wrong

• No browser window appears: on Windows x64 portable, headless is the supported mode. Check server status and the harmless page flow instead of repeatedly relaunching for a window.
• Command not found for camofox.cmd: check that the ZIP is extracted and your terminal is in the extracted folder. Use the bundled .\camofox.cmd, not a similarly named npm command from another installation.
• Browser status works, MCP is absent: confirm that the AI client is compatible, has the right config format, has restarted, and can launch npx. MCP is a separate installation/connection, not an option switched on inside the Browser ZIP.
• MCP responds but navigation fails: first test example.com, confirm the tab action and snapshot, and inspect the actual error. A server health response does not promise access to every website. Avoid “fixes” that turn off security controls or open local endpoints to the internet.

Your next step

Start with the official CamoFox Browser Windows x64 release. Unzip it, run version/start/status, and remember that headless means the browser works without a visible window. Once the Browser layer checks out, use the official MCP setup guide if your goal is an AI assistant controlling it. This order gives a beginner a clear answer when one part fails, rather than treating Browser, MCP and Camoufox as interchangeable downloads.