CamoFox Browser Server
Anti-detection browser server for AI agents — TypeScript REST API wrapping the Camoufox stealth browser engine
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
claude mcp add camofox-browser -- npx -y camofox-browser@2.5.0터미널에서 실행합니다.
{ "mcpServers": { "camofox-browser": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
Anti-detection browser server for AI agents — TypeScript REST API wrapping the Camoufox stealth browser engine
Anti-detection browser server for AI agents — REST API wrapping Camoufox engine with OpenClaw plugin support
The Problem: Standard browser automation (Puppeteer, Playwright, Selenium) is easily detected by modern anti-bot systems. JavaScript-level patches are fragile and get bypassed quickly.
The Solution: CamoFox Browser Server wraps Camoufox, a Firefox fork with C++ engine-level fingerprint spoofing. No JavaScript injection — anti-detection happens at the browser engine level.
userId (defaults: max 50 sessions, max 10 tabs/session)explicit-wins or proxy-locked)eN element references for precise interactionCAMOFOX_API_KEY is set)/start, /tabs/open, /act, etc.)CamoFox Browser Server is in Preview (Phase 1). Preview releases are functional for browser automation and agent integration, but carry specific compatibility commitments and explicit non-goals.
During Preview, CamoFox follows an additive-only deprecation model:
listItemId accepted alongside sessionKey, OpenClaw /act routing to core endpoints) continue to work alongside their replacementsBrowser profiles, download registries, and CLI session files use versioned sidecar formats. When upgrading CamoFox:
Supported sidecars include limited forward-migration paths (e.g., fingerprint v0 → v1); when no migration path exists for a given version, the server refuses to load the file and logs an actionable recovery message. There is no silent repair or downgrade path — this fail-closed default prevents data corruption at the cost of manual intervention on unsupported version jumps.
Requires Node.js 22+. Browser installation runs during npm install and fails if the
required engine cannot be downloaded, extracted, or validated. Downloads are streamed
to disk; extraction uses Python 3 on Linux (install python3 first), system tar on
macOS, and built-in PowerShell/.NET ZIP support on Windows. Keep sufficient disk space for both the ZIP and extracted engine.
Docker installs the engine once using the same installer. Optional GeoLite download
failures only produce a warning.
Set PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 only when deliberately deferring browser
provisioning (for example, a source-only CI build or an existing portable bundle).
Before launching, run npm run browser:install from the package directory with that
variable unset. A supported cache with a nonempty executable is reused without a
network update check. CAMOUFOX_INSTALL_DIR selects the cache directory. Existing
incomplete/unsupported caches are preserved and rejected: choose a new path with
CAMOUFOX_INSTALL_DIR to install afresh, and retain the old cache for diagnosis.
Missing engine/version errors require engine installation, not deleting profiles.
git clone https://github.com/redf0x1/camofox-browser.git
cd camofox-browser
npm install
npm run build
npm start
npm install -g camofox-browser
# Start the server
camofox-browser
# Or use the CLI for browser automation
camofox open https://example.com
camofox snapshot
camofox click e5
See CLI for the complete command reference.
Windows x64 is supported as a headless-first portable distribution. Release ZIPs are named camofox-browser-<version>-windows-x64.zip and contain the Node.js runtime, application runtime, and the pinned Camoufox Windows x64 engine, so a global Node.js installation is not required.
Extract the ZIP to a writable directory and run the bundled launchers from PowerShell or Command Prompt:
.\camofox.cmd --version
.\camofox.cmd server start --background
.\camofox.cmd server status
.\camofox.cmd server stop
Portable runtime state stays under data\home inside the extracted directory. This includes camofox-browser's .camofox profiles/logs and the bundled Camoufox cache, so the portable distribution does not use the normal Windows user profile for its application state.
The portable ZIP intentionally excludes Camoufox's upstream bundled fonts/ directory because the exact upstream source explicitly does not permit redistribution of those copyrighted Windows/macOS fonts. On Windows, CamoFox uses fonts installed on the host system instead.
The supported Windows x64 display contract is headless=true. headless=false and headless="virtual" are rejected with a clear error before any Linux-only display process is attempted. Xvfb/VNC virtual display mode remains Linux-only, and native headed Windows mode is not part of the verified support contract.
The release workflow verifies the ZIP after extracting it into a path containing spaces, starts the CLI using bundled Node.js with global Node removed from PATH, checks /health, runs a local create → navigate → snapshot → close browser flow, and confirms server shutdown and portable-state placement.
Docker image:
ghcr.io/redf0x1/camofox-browser
docker build -t camofox-browser .
docker run -d \
--name camofox-browser \
-p 9377:9377 \
-p 6080:6080 \
-e CAMOFOX_HOST=0.0.0.0 \
-e CAMOFOX_AUTH_MODE=auto \
-e CAMOFOX_API_KEY=change-me \
-v ~/.camofox:/home/node/.camofox \
camofox-browser
To persist browser profiles (cookies, localStorage, IndexedDB, etc.) across container restarts, keep the volume mount shown above.
services:
camofox-browser:
build: .
ports:
- "9377:9377"
environment:
CAMOFOX_HOST: "0.0.0.0"
CAMOFOX_PORT: "9377"
# auto requires CAMOFOX_API_KEY when CAMOFOX_HOST is non-loopback
CAMOFOX_AUTH_MODE: "auto"
CAMOFOX_API_KEY: "change-me"
# CAMOFOX_ADMIN_KEY: "change-me"
# Optional: proxy routing (also enables Camoufox geoip mode)
# PROXY_HOST: ""
# PROXY_PORT: ""
# PROXY_USERNAME: ""
# PROXY_PASSWORD: ""
curl http://localhost:9377/health
# {"ok":true,"engine":"camoufox","browserConnected":true}
CamoFox Browser includes a powerful CLI for browser automation directly from the terminal. The CLI auto-starts the server when needed.
# Global install (recommended)
npm install -g camofox-browser
# Or use npx (no install needed)
npx camofox-browser open https://example.com
camofox open https://example.com # Open a page in anti-detection browser
camofox snapshot # Get accessibility tree with element refs
camofox click e5 # Click element [e5]
camofox type e3 "hello world" # Type into element [e3]
camofox screenshot --output page.png # Save screenshot
camofox close # Close the tab
# Browser lifecycle
camofox open <url> # Open URL in new tab
camofox close [tabId] # Close tab
camofox navigate <url> # Navigate current tab to URL
# Inspection
camofox snapshot # Get accessibility tree with [eN] refs
camofox screenshot [--output file] # Take screenshot (saves to file)
camofox annotate # Screenshot + element ref overlay
camofox get-url # Get current page URL
camofox get-text # Get page text content
camofox get-links # Get all links on page
camofox get-tabs # List open tabs
camofox extract-structured @schema.json # Extract deterministic JSON from a schema
# Interaction
camofox click <ref> # Click element by ref
camofox type <ref> <text> # Type text into element
camofox fill '[e1]="user" [e2]="pw"' # Fill multiple fields at once
camofox scroll <direction> # Scroll up/down/left/right
camofox select <ref> <value> # Select dropdown option
camofox hover <ref> # Hover over element
camofox press <key> # Press keyboard key
# Navigation
camofox go-back # Browser back
camofox go-forward # Browser forward
camofox search "query" --engine google # Search (8 engines supported)
camofox eval "document.title" # Execute JavaScript
camofox wait <selector> [--timeout ms] # Wait for element
Text input: CamoFox has no character limit for typed or filled text. Short text stays humanized for anti-detection, while long text automatically switches to bulk DOM insertion so large inputs do not truncate.
camofox session save <name> # Save current browser state
camofox session load <name> # Restore browser state
camofox session list # List saved sessions
camofox session delete <name> # Delete saved session
camofox cookie export <file> # Export cookies to JSON file
camofox cookie import <file> # Import cookies from JSON file
Securely store credentials locally with AES-256-GCM encryption. Credentials are never output to stdout — safe for LLM agent automation.
camofox auth save <profile> [--url URL] # Save credentials (prompts for master password)
camofox auth load <profile> # Show profile info (username only)
camofox auth list # List saved profiles (no secrets shown)
camofox auth delete <profile> # Delete a profile
camofox auth change-password <profile> # Change master password
# Inject credentials into a browser tab (LLM-safe)
camofox snapshot # Get element refs first
camofox auth load gmail --inject --username-ref e5 --password-ref e12
Security: Master passwords use Argon2id KDF (with PBKDF2 fallback). Vault files are stored with 0600 permissions. The
--injectflag sends credentials directly to the browser — the LLM agent never sees the password.
Execute multiple commands from a file for automation workflows:
# Create a script
cat > login-flow.txt << 'EOF'
# Login automation script
open https://example.com/login
snapshot
type e3 "username"
type e5 "password"
click e7
wait .dashboard --timeout 5000
screenshot --output result.png
close
EOF
# Run it
camofox run login-flow.txt
# Continue on errors
camofox run login-flow.txt --continue-on-error
# Read from stdin
echo "get-url" | camofox run -
camofox server start # Start server daemon
camofox server start --background # Start in background
camofox server stop # Stop server daemon
camofox server status # Check server status
camofox health # System health report
camofox version # CLI + server version
camofox info # Configuration info
camofox console [tabId] # View console messages
camofox console [tabId] --type error # Filter by type (log/warning/error/info/debug)
camofox console [tabId] --clear # View then clear messages
camofox errors [tabId] # View uncaught JavaScript errors
camofox errors [tabId] --clear # View then clear errors
camofox trace start [tabId] # Start recording trace
camofox trace stop [tabId] [-o file.zip] # Stop and save trace ZIP
camofox trace chunk-start [tabId] # Start new trace chunk
camofox trace chunk-stop [tabId] [-o f] # Stop chunk and save ZIP
camofox trace status [tabId] # Check active trace status
View traces at trace.playwright.dev
camofox get-url --format json # {"url":"https://example.com"}
camofox get-url --format text # URL: https://example.com
camofox get-url --format plain # https://example.com
Tip: Use
--format jsonfor programmatic parsing and LLM agent integration.
CamoFox uses Camoufox, a Firefox fork with C++ level fingerprint spoofing. Unlike Chromium-based tools, CamoFox passes bot detection on Google, Cloudflare, and other anti-bot services.
0600 permissions--inject flag sends credentials directly to the browser — the LLM agent orchestrating the CLI never sees raw passwordsCamoFox works seamlessly with AI coding agents and LLM-powered automation:
Add CamoFox skills to your AI coding assistant for full browser automation context:
npx skills add redf0x1/camofox-browser
This works with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Goose, OpenCode, Windsurf, and 40+ other agents.
Available skills:
The installer will prompt you to choose which skills and which agents to configure.
npx skills add redf0x1/camofox-browser
# Installs to .claude/skills/camofox-browser/SKILL.md
npx skills add redf0x1/camofox-browser
# Installs to .agents/skills/ directory
Tip: Skills are symlinked from the repo, so they stay up to date. Do not manually copy
SKILL.mdfiles.
Use CamoFox MCP for direct integration with Claude, Cursor, Windsurf, and other MCP-compatible agents. See Used With.
AI agents can use the CLI with --format json for structured output:
camofox open https://example.com # Open page
camofox snapshot --format json # Get structured element tree
camofox click e5 # Interact with elements
camofox auth load gmail --inject --username-ref e5 --password-ref e12 # Safe credential injection
Create reusable automation scripts that AI agents can execute:
camofox run automation-flow.txt # Execute multi-step workflow
AI Agent (MCP / OpenClaw / REST Client)
│
▼ HTTP REST API (port 9377)
┌──────────────────────────────────────────┐
│ CamoFox Browser Server │
│ (Express + TypeScript) │
├──────────────────────────────────────────┤
│ Routes Services │
│ ├── Core API ├── Browser │
│ └── OpenClaw compat ├── Session │
│ └── Tab ops │
├──────────────────────────────────────────┤
│ Camoufox Engine (anti-detect) │
│ Firefox fork + engine-level spoofing │
└──────────────────────────────────────────┘
userId runs in its own persistent Firefox process/context (backed by launchPersistentContext(userDataDir))~/.camofox/profiles/ (override via CAMOFOX_PROFILES_DIR). Linux/macOS keep the readable default-user directory name; new Windows profiles use a deterministic hashed directory name so case-insensitive or trailing-dot/space-equivalent user IDs cannot share a Firefox profile. Existing Windows directories from the previous layout are read in place only when their exact on-disk name is unambiguous and no hashed directory also exists; conflicting layouts fail closed with both recovery paths in the error.Base URL: http://localhost:9377
Security defaults:
CAMOFOX_HOSTnow defaults to127.0.0.1, andCAMOFOX_AUTH_MODE=autokeeps local loopback usage open while requiringCAMOFOX_API_KEYwhen you bind beyond loopback (for example0.0.0.0in Docker or PaaS). SetCAMOFOX_AUTH_MODE=requiredto require API-key auth everywhere. SetCAMOFOX_AUTH_MODE=disabledonly for trusted private agent networks whose clients cannot send bearer tokens; this disables API-key auth for protected endpoints and keeps private-network navigation blocked. On non-loopback binds, navigation targets on loopback/private/link-local/metadata hosts are blocked by default unless you explicitly setCAMOFOX_ALLOW_PRIVATE_NETWORK=true. If you also configurePROXY_HOST/PROXY_PORT, exposed deployments must opt intoCAMOFOX_ALLOW_PRIVATE_NETWORK=trueuntil proxy-side private-target validation exists.
The Camofox Browser API includes OpenAPI 3.1.0 docs for a representative subset of the shipped route surface:
The OpenAPI spec covers a representative subset of core and OpenClaw endpoints, including request schemas, response shapes, authentication requirements, and validation rules.
Note: For any endpoint that targets an existing tab (/tabs/:tabId/...), the server resolves tabId within a userId scope. If you omit userId from the request body, the server returns 400 { "error": "userId is required" }. If userId is present but the tab belongs to a different user, the server returns 404 Tab not found — except DELETE /tabs/:tabId, which is idempotent and returns 200 { "ok": true } when no matching tab is found under the given userId scope (the tab is already gone from the caller's perspective). For endpoints that accept userId as a query parameter (e.g. GET /tabs/:tabId/snapshot), omitting it may also result in a 400 or 404 depending on the route.
POST /sessions/:userId/toggle-display
{"headless": "virtual"}
Auth: Conditional — requires Authorization: Bearer $CAMOFOX_API_KEY when CAMOFOX_AUTH_MODE=required or when auto mode has an API key configured. No auth is required in CAMOFOX_AUTH_MODE=disabled.
Switch browser between headless and headed mode. When encountering CAPTCHAs or issues requiring visual interaction, switch to headed mode to show the browser window.
Platform note: The Windows x64 contract is headless-only. Requests with headless: false or headless: "virtual" return HTTP 400 on Windows. The Xvfb/VNC behavior described below is Linux-only.
Returns:
{"ok": true, "headless": "virtual", "vncUrl": "http://localhost:6080/vnc.html?autoconnect=true&resize=scale&token=...", "message": "Browser visible via VNC", "userId": "agent1"}
Note: This restarts the browser context. All tabs are invalidated but cookies/auth state persist via the persistent profile.
On Linux, when the display mode is set to "virtual" or a headed request requires a virtual display, the server can start a VNC viewer accessible via web browser.
# 1. Switch to virtual mode
POST /sessions/:userId/toggle-display
{"headless": "virtual"}
# Response includes vncUrl — open in browser to see Firefox
# 2. Solve CAPTCHA or interact with the browser
# 3. Switch back to headless
POST /sessions/:userId/toggle-display
{"headless": true}
# VNC automatically stops
The VNC session auto-terminates after 2 minutes (configurable via CAMOFOX_VNC_TIMEOUT_MS).
Execute a JavaScript expression in the page context and return the JSON-serializable result.
Auth: required when CAMOFOX_AUTH_MODE=required or when auto mode has an API key configured; no auth is required in CAMOFOX_AUTH_MODE=disabled.
Note: async expressions must be wrapped in an async IIFE (for example, (async () => { ... })()). Top-level await is not supported.
POST /tabs/:tabId/evaluate
{"userId": "agent1", "expression": "document.title"}
Returns: {"ok": true, "result": "Page Title", "resultType": "string", "truncated": false}
Execute a long-running JavaScript expression (up to 300s timeout). Conditionally API-key protected. Rate limited.
Auth: required when CAMOFOX_AUTH_MODE=required or when auto mode has an API key configured; no auth is required in CAMOFOX_AUTH_MODE=disabled.
Note: async expressions must be wrapped in an async IIFE (for example, (async () => { ... })()). Top-level await is not supported.
POST /tabs/:tabId/evaluate-extended
{"userId": "agent1", "expression": "(async () => { const response = await fetch('/api/data'); return await response.json(); })()", "timeout": 60000}
Returns: {"ok": true, "result": {...}, "resultType": "object", "truncated": false}
OpenClaw-compatible aliases (used by the OpenClaw plugin).
Structured extract returns deterministic JSON from a DOM schema without arbitrary JavaScript. Use it when you want stable data contracts instead of ad-hoc evaluate() calls.
Core API:
curl -X POST "$CAMOFOX_URL/tabs/$TAB_ID/extract-structured" \
-H 'Content-Type: application/json' \
-d '{
"userId": "agent1",
"schema": {
"kind": "object",
"fields": {
"title": { "kind": "text", "selector": "h1", "required": true, "trim": true },
"products": {
"kind": "list",
"selector": ".product",
"item": {
"kind": "object",
"fields": {
"name": { "kind": "text", "selector": ".name", "required": true, "trim": true },
"href": { "kind": "url", "selector": "a.product-link", "attr": "href", "required": true }
}
}
}
}
}
}'
CLI:
camofox extract-structured @schema.json <tabId> --user <userId> --format json
OpenClaw:
curl -X POST "$CAMOFOX_URL/act" \
-H 'Content-Type: application/json' \
-d '{
"kind": "extractStructured",
"targetId": "tab-123",
"userId": "agent1",
"schema": {
"kind": "object",
"fields": {
"title": { "kind": "text", "selector": "h1", "required": true }
}
}
}'
Notes:
fieldPathnull / null / []Use macros via POST /tabs/:tabId/navigate with { "macro": "@google_search", "query": "..." }.
Built-in presets (also exposed via GET /presets):
Create a tab with a preset:
curl -X POST http://localhost:9377/tabs \
-H 'Content-Type: application/json' \
-d '{"userId":"agent1","sessionKey":"task1","preset":"japan","url":"https://example.com"}'
Custom presets: set CAMOFOX_PRESETS_FILE=/path/to/presets.json (JSON object; keys become preset names).
CamoFox supports session-level proxy and geolocation configuration with a hybrid model that combines server defaults with per-session overrides.
Server-level baseline (via environment variables):
PROXY_HOST, PROXY_PORT, PROXY_USERNAME, PROXY_PASSWORD — applied as the default for all sessionsSession-level overrides (via POST /tabs or CLI):
proxyProfile — select a named proxy profile from CAMOFOX_PROXY_PROFILES_FILEproxy — provide raw proxy fields (host, port, username, password) directlyuserId + sessionKey combinationSession identity rules:
userId may run different sessionKey profiles in parallel with different proxy/geo configurationsuserId + sessionKey combination maintains a stable proxy/geo identity — requests with conflicting proxy/geo fields are rejecteduserId + sessionKey, not just userIdCamoFox offers two geo modes that control how explicit geo fields (locale, timezone, geolocation) interact with proxy-derived geo:
geoMode=explicit-wins (default):
geoMode=proxy-locked:
Session-level proxy with named profile:
camofox open https://example.com --proxy-profile tokyo-exit --user agent1
Session-level proxy with raw fields:
camofox open https://example.com \
--proxy-host proxy.example.com \
--proxy-port 8080 \
--proxy-username user \
--proxy-password pass \
--user agent1
Combine proxy with geo mode:
camofox open https://example.com \
--proxy-profile london-exit \
--geo uk \
--geo-mode proxy-locked \
--user agent1
Using a named proxy profile with explicit geo:
curl -X POST http://localhost:9377/tabs \
-H 'Content-Type: application/json' \
-d '{
"userId": "agent1",
"sessionKey": "task1",
"url": "https://example.com",
"proxyProfile": "tokyo-exit",
"preset": "japan",
"geoMode": "explicit-wins"
}'
Using raw proxy fields with proxy-locked geo:
curl -X POST http://localhost:9377/tabs \
-H 'Content-Type: application/json' \
-d '{
"userId": "agent1",
"sessionKey": "task2",
"url": "https://example.com",
"proxy": {
"host": "proxy.example.com",
"port": 8080,
"username": "user",
"password": "pass"
},
"geoMode": "proxy-locked"
}'
Define proxy profiles in a JSON file and point CAMOFOX_PROXY_PROFILES_FILE to it:
{
"tokyo-exit": {
"server": "http://tokyo.proxy.example.com:8080",
"username": "user",
"password": "pass"
},
"london-exit": {
"server": "http://london.proxy.example.com:8080"
}
}
Then use profiles by name in API requests or CLI commands.
CAMOFOX_OSandCAMOFOX_SCREEN_*are generation-time controls: they affect only newly generated fingerprints and have no effect while an existingfingerprint.jsonsidecar is in use. Reset the profile or deletefingerprint.jsonto force regeneration under the new defaults.CAMOFOX_ALLOW_WEBGLandCAMOFOX_HUMANIZEare launch-time overrides and apply on every browser launch regardless of whether a sidecar is reused.
CamoFox implements a two-stage idle lifecycle for graceful cleanup and daemon exit:
Stage 1 — Idle Cleanup
CAMOFOX_IDLE_TIMEOUT_MS of idle time (default: 30 minutes), the server runs cleanup to close idle sessions and tabsStage 2 — Daemon Exit
CAMOFOX_IDLE_EXIT_TIMEOUT_MS (default: matches Stage 1 timeout)Activity detection:
This two-stage model ensures cleanup runs before daemon exit, preventing resource leaks while allowing the server to shut down cleanly when fully idle.
docker build -t camofox-browser .
docker run -p 9377:9377 -p 6080:6080 \
-v ~/.camofox:/home/node/.camofox \
-e CAMOFOX_HOST=0.0.0.0 \
-e CAMOFOX_PORT=9377 \
-e CAMOFOX_AUTH_MODE=auto \
-e CAMOFOX_API_KEY=change-me \
camofox-browser
For private Docker networks used by agents such as Hermes, OpenClaw, or GoClaw that cannot send a bearer token, keep the service off published host ports and disable API-key auth explicitly:
docker network create camofox-agents
docker run -d \
--name camofox-browser \
--network camofox-agents \
-e CAMOFOX_HOST=0.0.0.0 \
-e CAMOFOX_AUTH_MODE=disabled \
-v ~/.camofox:/home/node/.camofox \
camofox-browser
Then configure the agent with CAMOFOX_URL=http://camofox-browser:9377 from another container on the same Docker network. Do not combine CAMOFOX_AUTH_MODE=disabled with public port publishing or CAMOFOX_ALLOW_PRIVATE_NETWORK=true.
This repo includes a starter fly.toml for one-command deploys.
fly launch
fly deploy
CAMOFOX_HOST=0.0.0.0CAMOFOX_API_KEY to a strong secretCAMOFOX_PORT=9377 (Railway will also provide PORT, which is supported)93779377CAMOFOX_HOST=0.0.0.0CAMOFOX_API_KEY to a strong secretCAMOFOX_PORT=9377 (or rely on Render PORT)src/
├── cli/
│ ├── commands/ # Command modules (core, navigation, interaction, etc.)
│ │ ├── console.ts # Console capture commands
│ │ └── trace.ts # Playwright tracing commands
│ ├── vault/ # Auth vault (encryption, storage)
│ ├── server/ # Server lifecycle management
│ ├── transport/ # HTTP transport layer
│ ├── output/ # Output formatting
│ └── utils/ # Shared utilities
├── server.ts # Express app entry point
├── types.ts # Shared TypeScript interfaces
├── routes/
│ ├── core.ts # Core REST API (~42 endpoints)
│ └── openclaw.ts # OpenClaw compatibility (~7 endpoints)
├── services/
│ ├── browser.ts # Browser lifecycle + persistent context pool
│ ├── batch-downloader.ts # Batch download orchestrator
│ ├── context-pool.ts # Browser context pool with LRU eviction
│ ├── download.ts # Download tracking service
│ ├── health.ts # Browser health tracking
│ ├── resource-extractor.ts # Page resource extraction
│ ├── session.ts # Session management + limits
│ ├── tab.ts # Tab operations (snapshot/click/type/etc.)
│ ├── tracing.ts # Playwright tracing service
│ ├── vnc.ts # VNC/virtual display lifecycle
│ └── youtube.ts # YouTube transcript extraction
├── middleware/
│ ├── auth.ts # API/admin auth helpers
│ ├── errors.ts # Error handling
│ ├── logging.ts # Structured logging
│ └── rate-limit.ts # In-memory rate limiter
└── utils/
├── config.ts # Environment config parsing
├── cookies.ts # Cookie utilities
├── download-helpers.ts # Download helper functions
├── launcher.ts # Browser launcher utilities
├── macros.ts # Search macro expansion
├── presets.ts # Geo preset definitions/loader
└── snapshot.ts # Snapshot truncation/windowing
See CONTRIBUTING.md
This project is based on camofox-browser by Jo Inc (YC W24) and the Camoufox anti-detection browser engine by daijro.
Sketchy people are doing sketchy things with crypto tokens named "Camofox" now that this project is getting attention. Camofox is not a crypto project and will never be one. Any token, coin, or NFT using the Camofox name has nothing to do with us.
Anti-detection browser server for AI agents — REST API wrapping Camoufox engine with OpenClaw plugin support
{ "mcpServers": { "camofox-browser": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Camofox Browser은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-16. Anti-detection browser server for AI agents — REST API wrapping Camoufox engine with OpenClaw plugin support