Clearcote Browser MCP
A Chromium with engine-level device fingerprint spoofing and an MCP server that lets an agent drive it through Playwright
- 254 ★ on the repository
- Last commit
- BSD-3-Clause
Broad access
Why this level
- Fingerprint spoofing lets automation pass anti-bot checks, and acting against a site's rules leads to account bans and legal exposure
- The agent gets a full browser with cookies, form input and JavaScript execution on pages
- A proxy login and cloud key sit in the client config, and the browser binary downloads on first run
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/clearcote-browserDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Fingerprint spoofing lets automation pass anti-bot checks, and acting against a site's rules leads to account bans and legal exposure
- The agent gets a full browser with cookies, form input and JavaScript execution on pages
- A proxy login and cloud key sit in the client config, and the browser binary downloads on first run
This is third-party code. Review the repository files before installing.
What it does
Clearcote is a Chromium build based on ungoogled-chromium where fingerprint controls are compiled into the C++ engine. The page's scripts, the HTTP headers and the TLS handshake all come from one real Chromium and agree with each other, so the browser presents one coherent machine. The same seed always yields the same profile. The browser is driven by Playwright or Puppeteer code, with SDKs for Python, Node.js and .NET. For agents the `mcp/` directory holds the `clearcote-mcp` server: about 20 tools around one shared browser. Reading: `read_page` (Markdown, text or both), `get_page_html`, `page_elements`, `evaluate_js`, `get_cookies`. Actions: `navigate`, `click`, `fill_field`, `press_key`, tab handling. Capture: `screenshot_page`, `save_page_pdf`. Sessions: `save_profile` and `load_profile` store cookies and storage. The `get_cdp_endpoint` tool hands the same browser to any CDP client such as Playwright, browser-use or Crawl4AI. The persona is set through environment variables: `CLEARCOTE_FINGERPRINT`, `CLEARCOTE_PLATFORM`, `CLEARCOTE_BRAND`, `CLEARCOTE_PROXY` and `CLEARCOTE_GEOIP` (timezone, locale and WebRTC IP derive from the proxy exit address). The binary downloads on first run with a SHA-256 check. Hosted browsers on Clearcote's servers switch on through `CLEARCOTE_CLOUD` and `CLEARCOTE_API_KEY`.
Who it is for. Scraper developers, testers and automation teams that need a stable browser profile for an agent and a way to check their own sites' defenses.
Good fit when
- An agent must work in one browser profile between runs: the same seed gives the same "machine"
- You already have Playwright code and only need to change the launch line to the SDK's `launch()`
- You need to see how your own site or anti-bot defense reacts to different device profiles
- Claude or Cursor should read pages and fill forms over MCP while Playwright and browser-use attach to the same browser over CDP
- You need a reproducible build: the open build is assembled from the repository's source patches
Not a fit when
- You would act on other people's sites against their rules: fingerprint spoofing breaks many services' terms and gets accounts blocked
- Plain Playwright on your own sites solves the task: a regular browser is simpler and needs no separate binary
- Your platform is macOS on Apple Silicon: builds exist for Windows x64, Linux x64 and Docker
- You only need to read open pages without profiles: an ordinary browser MCP is enough
Example request
Connect clearcote-mcp, open our login page in the persistent acct-1 profile and check that the form accepts test dataMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
CLEARCOTE_FINGERPRINT- Seed string for a stable device identity
CLEARCOTE_PROXYsecret- Proxy address like http://user:pass@host:port for all traffic
CLEARCOTE_API_KEYsecret- The cc_live_... key for cloud browsers and the run_task tool
Limitations
- Native builds exist for Windows x64, Linux x64 and Docker. macOS is not in the platform table.
- The latest build is free for one browser with a GitHub sign-in, the Pro plan costs 49 dollars a month and hosted browsers are billed per gigabyte.
- Proxy and cloud key travel in environment variables of the MCP config, so the file holding them must not be committed.
- The project carries a DISCLAIMER.md: responsibility for use lies with the person, and fingerprint spoofing conflicts with some sites' rules.
How to disable. Remove the clearcote entry from mcpServers in the client config and restart it. The downloaded browser binary sits in the SDK cache and can be deleted by hand. The Python package comes off with pip uninstall clearcote-mcp.
FAQ
How do I connect Clearcote to Claude Desktop or Cursor?
Add an `mcpServers` entry with command `npx` and args `["-y", "clearcote-mcp"]`, and set `CLEARCOTE_FINGERPRINT` in env. It launches through uvx, pipx or pip and downloads the browser on first start.
How is Clearcote different from puppeteer-stealth?
The spoofing is done in Chromium's C++ engine rather than JavaScript patches over the page. The author holds that JavaScript patches give themselves away. Control goes over CDP with no automation flags, so `navigator.webdriver` stays `false`.
How do I give the same browser to Playwright or browser-use?
Call the `get_cdp_endpoint` tool or run `clearcote-serve --port 9222`. The client attaches at http://127.0.0.1:9222, for example with `chromium.connect_over_cdp`.
How much does Clearcote cost?
The open build is free. The latest build is free for one browser with a GitHub sign-in, Pro costs 49 dollars a month and hosted browsers 1 euro per gigabyte.
Is it legal to use Clearcote?
The browser itself is open source, and the law and site rules depend on the task. Testing your own sites and collecting public data differ from signing in to other people's accounts, so check the platform's terms before running.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally
Agent browser on direct CDP without Playwright: login profiles, a CLI, an MCP server and recording workflows into a skill
An MCP server that opens pages in headless Chromium through Playwright and hands the agent the main text as Markdown, even from JavaScript-heavy sites
Browserless.io MCP server: a cloud browser for the agent with page reads, site crawls, Lighthouse audits and click-driven sessions
A Rust browser engine without Chromium, with its own TLS fingerprint and V8; the MCP server gives agents pages and protection checks.
Microsoft's official MCP server for driving a browser with Playwright through the accessibility tree, no screenshots needed
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Clearcote Browser (this card) | yes | not required | 254 | |
| Anti-Detect Browser Skills (AntiBrow) | yes | 21 | skills with fingerprint profiles and data collection recipes, while here it is the Chromium itself with engine-level spoofing plus an MCP server | |
| Playwright MCP | yes | not required | 39,570 | a regular Chromium with no fingerprint spoofing, while Clearcote gives the agent a coherent device profile |
README in short
The page explains the coherent fingerprint idea, gives a Python quickstart and an at-a-glance table of what it is, what it works with, where it runs and what it costs. Then it lays out how to run it: SDK, CDP endpoint, Docker, cloud, MCP server and agent runs. A separate section shows how to move code from Playwright, Puppeteer, browser-use, Crawl4AI, nodriver, Stagehand and closed anti-detect browsers.