Camofox Mcp

Name: Camofox Mcp
Author: redf0x1

@redf0x1

Repository

About Camofox Mcp

No overview available yet

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "camofox-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-d",
        "-p",
        "9377:9377",
        "--name",
        "camofox-browser",
        "ghcr.io/redf0x1/camofox-browser:latest"
      ]
    }
  }
}

Tools

export cookies from an active tab and save them under a profile name

load a saved profile into an active tab (imports cookies)

list all saved profiles and metadata

delete a saved profile permanently

Overview

What is Camofox MCP?

Camofox MCP is an MCP (Model Context Protocol) server that wraps the CamoFox Browser Server to give AI agents a web automation layer with anti-detection fingerprinting. It is for developers and AI agent users who need to browse, interact, and automate websites without being blocked by bot detection systems.

How to use Camofox MCP?

Camofox MCP requires two components: camofox-browser (a headless anti-detection Firefox server) and camofox-mcp (the MCP bridge). Start the browser via Docker, npx camofox-browser@latest, or from source. Then configure an MCP-compatible client (VS Code, Claude Desktop, or Cursor) with a JSON config that sets the CAMOFOX_URL environment variable to http://localhost:9377. After setup, restart your editor and paste the provided verification prompt into your AI agent.

Key features of Camofox MCP

Anti-detection fingerprinting per tab
Accessibility tree snapshots (90% fewer tokens than screenshots)
Built-in search macros for 14 engines
Session persistence via cookie import/export
CSS selector fallback for element targeting
35 tools covering tab, navigation, interaction, and batch actions

Use cases of Camofox MCP

Automating web tasks that require bypassing CAPTCHAs and fingerprint detection
Scraping or testing websites that block standard Playwright automation
Maintaining logged-in sessions across multiple interactions
Performing region-specific browsing with geo presets

FAQ from Camofox MCP

What dependencies does Camofox MCP require?

Camofox MCP requires the CamoFox Browser Server to be running (via Docker, npx, or source) and either Docker or Node.js 18+. The MCP client must be an MCP-compatible editor (VS Code, Cursor, Claude Desktop).

How does Camofox MCP differ from Playwright MCP?

Camofox MCP adds anti-detection fingerprinting, passes bot detection tests, offers 14 search engine macros, and provides cookie import/export. Playwright MCP lacks these features but has simpler setup.

How does Camofox MCP compare to other Camoufox MCPs?

Camofox MCP exposes 35 tools, uses a REST API client architecture (not direct browser control), supports session persistence, search macros, CSS selector fallback, and is actively maintained.

Where does data and state live?

Browser data (sessions, cookies, profiles) lives inside the CamoFox Browser Server instance. The MCP server communicates with it over REST and does not store data itself.

What transport and authentication does Camofox MCP use?

Camofox MCP uses stdio transport for MCP communication. Authentication is not mentioned; the browser server listens on HTTP (port 9377) and is assumed to be local or network-restricted. Some tools (e.g., camofox_evaluate_js) may require an API key configured server-side.