Browseforge, developed by Nczz, is an automation-ready anti-detect browser workspace. It creates repeatable, isolated browser identities for teams across various workflows. The core server component uses Go, with Node.js for scripts and Playwright integration. Python is often used for client-side AI agent orchestration. Distributed as Docker images and portable binaries, Browseforge supports both native linux/amd64 and linux/arm64 architectures. It provides essential tools for browser automation and AI agent control.

What does Browseforge connect to?

Browseforge connects to multiple browser runtimes, including Firefox via Camoufox, Chromium via CloakBrowser, and its own source-level BrowseForge Chromium runtime. It operates as an anti-detect browser workspace, ensuring isolated browser identities. Additionally, it functions as an MCP (Model Context Protocol) server. This design places it firmly within the category of browser automation tools, offering diverse runtime options for various operational needs. Its architecture supports distinct browser environments for specialized tasks.

Core features and tools

Browseforge exposes several callable tools. For MCP, it offers a web_search tool supporting Google, Bing, or DuckDuckGo. YAML workflows include actions like create_profile, open_browser, close_browser, navigate, click, type, eval, wait, screenshot, and sleep. Its Playwright integration provides a compatible WebSocket endpoint for running sessions, allowing external Playwright clients to attach. AI agents access browser control tools such as navigate, click, scroll, and snapshot for autonomous operations.

Who is it for?

Browseforge serves QA and automation teams validating multi-account or multi-region browser flows. It also assists browser-runtime researchers comparing fingerprint and anti-detection behavior. AI agent builders needing MCP-controlled browser sessions are a key audience. Operators requiring repeatable profile storage, backup, restore, and remote browser access will also find it useful. This is not the right fit if you require a browser automation tool that does not support isolated browser identities.

How to get started

The server authenticates using a Bearer token for REST API, MCP HTTP, and Playwright proxy access. API keys for AI agent integration are managed via configuration files like mcp_agent.secrets.yaml, and Streamable HTTP is a supported transport protocol.

Use cases

• Running isolated browser identities for automation without rebuilding automation around each browser engine.
• Controlling browser profiles and sessions programmatically through its REST API, MCP tools, YAML workflows, or Playwright clients.
• Enabling AI agents to autonomously navigate, click, scroll, and summarize websites based on natural language commands.

Browseforge offers a specialized browser workspace for teams needing isolated browser identities and automation. Its Go and Node.js foundation supports various browser runtimes and integrations, including Playwright and AI agents. The platform provides tools for programmatic control and supports multiple transport protocols for agent communication. Its token-authenticated access secures operations for diverse user groups. Try controlling browser profiles programmatically using its REST API.