Camoufox Mcp
Give your coding agent a stealth Firefox browser for scraping and automation when normal headless browsers get blocked.
Overview
io.github.baixianger/camoufox-mcp is a Build-phase MCP server that exposes anti-detection Camoufox (stealth Firefox) browser automation to AI agents for web scraping and scripted browsing.
What is this MCP server?
- Camoufox-based anti-detection Firefox automation exposed as an MCP stdio server (npm package camoufox-mcp v1.0.0)
- Purpose-built for web scraping and automation where fingerprinting and bot checks block vanilla browsers
- stdio transport fits Claude Code, Cursor, and other MCP hosts without running a separate HTTP gateway
- Pairs with agent workflows that need navigate, extract, and repeat across hostile or rate-limited sites
- GitHub source at baixianger/camoufox-mcp for local install and config alongside your agent
- Catalog schema version 1.0.0
- 1 npm package: camoufox-mcp with stdio transport
- Repository: github.com/baixianger/camoufox-mcp
What problem does it solve?
Agents that rely on ordinary headless browsers often fail on sites that fingerprint traffic, leaving you without reliable automated access to competitor pages, listings, or dashboards.
Who is it for?
Indie builders running Claude Code or Cursor agents that must scrape or automate pages protected by bot detection, without outsourcing to a managed browser farm.
Skip if: Teams that only need official REST APIs, static documentation, or lightweight HTTP fetches with no JavaScript or anti-bot layer.
What do I get? / Deliverables
After you add the stdio MCP server, your agent can drive a stealth Firefox session locally and complete scrape-and-automate tasks that standard browser stacks reject.
- Registered stdio MCP server your agent can invoke for stealth browser sessions
- Agent-driven page navigation and extraction against anti-detection targets
- Repeatable scraping or automation flows without maintaining separate one-off browser scripts
Recommended MCP Servers
Journey fit
Browser automation is wired into the product during Build when agents need live web data or scripted page flows. Integrations is the right shelf because Camoufox MCP is an external runtime bridge (stdio npm server), not a UI or backend app module.
How it compares
MCP browser-integration server, not a hosted scraping SaaS or a Playwright test skill.
Common Questions / FAQ
Who is io.github.baixianger/camoufox-mcp for?
Solo and indie developers who ship AI agents and need stealth Firefox automation when normal headless browsers get blocked during scraping or workflow automation.
When should I use io.github.baixianger/camoufox-mcp?
Use it in the Build integrations phase when your agent must interact with real web pages under anti-detection constraints, especially for recurring scrape or navigate-extract loops.
How do I add io.github.baixianger/camoufox-mcp to my agent?
Install the npm package camoufox-mcp, configure it as an MCP stdio server in Claude Code, Cursor, or another MCP host, and point the entry at the published server from the baixianger/camoufox-mcp repository.