camofox-mcp
camofox-mcp is an MCP server that exposes a separate CamoFox browser server to MCP-compatible AI clients (stdio for local desktop clients; an optional HTTP mode for remote clients). It provides a toolset for web navigation, interaction, observation/extraction, downloads, and session/profile reuse.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS requirements and transport security details are not explicit in the provided README. Authentication (CAMOFOX_API_KEY) is mentioned only as a pass-through to the underlying browser server if it is enabled. Because it is a browser-control surface, session profiles may include sensitive cookies; isolation of the browser server and limiting exposure of MCP endpoints over the network are recommended. Dependency list is small but no vulnerability/SBOM data was provided, so hygiene is estimated.
⚡ Reliability
Best When
You can run an isolated camofox-browser service and connect camofox-mcp via stdio for local clients, or via HTTP only in a tightly controlled network.
Avoid When
Avoid exposing the HTTP transport broadly to untrusted networks or clients, and avoid using session profiles/cookies in shared environments.
Use Cases
- • Agent-driven web browsing and automation with an MCP client (navigation, clicking/typing, extraction).
- • Session persistence/cookie import for continuing browsing tasks across runs.
- • Remote MCP client integration via HTTP transport (e.g., OpenClaw-style setups).
- • Batch/multi-tab workflows with tracked state and cleanup.
Not For
- • Directly running as a standalone browser (must run a compatible camofox-browser server).
- • Highly sensitive/regulated environments where exposing browser-control endpoints over networks is unacceptable.
- • Environments where anti-detection/stealth behavior is disallowed by policy.
Interface
Authentication
Authentication appears to be delegated to the underlying camofox-browser server. The README notes that if the browser server enforces authentication, the same CAMOFOX_API_KEY must be configured on both sides.
Pricing
No pricing information provided; package appears MIT-licensed and distributed via npm/docker images.
Agent Metadata
Known Gotchas
- ⚠ Must run camofox-browser separately and ensure CAMOFOX_URL points to it.
- ⚠ Choose stdio for desktop/local clients; HTTP mode is mainly for remote MCP clients.
- ⚠ Accessibility-tree is the primary interaction model; some SPA/custom-component pages may require CSS-selector or rendered-HTML-based tools.
- ⚠ Session profiles can contain sensitive cookies; treat storage accordingly.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for camofox-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.