README 소개

** 지원 OS : 리눅스 및 macOS.** macOS 포트는 기본 크롬(visible)을 사용합니다. 또는 --headless=new) 및 X11이 필요하지 않습니다. Windows는 지원되지 않습니다. macOS 설정에 대한 docs/macos.md, 프로젝트 로컬 크롬 참조 테스트 및 런타임 세부 사항.

[!주의사항] 프로필당 한 브라우저 — 여러 MCP 클라이언트 프로세스가 공유됩니다. ·

• 정상 사용은 제한자를 결코 여행하지 않습니다: pace_warning 15+에서만 불 분당 검색 순차적 또는 가벼움의 사용은 아래에 있습니다.
• 경고는 고문, 블록이 아닙니다 : 검색은 실행합니다. 하지만 Google 총 볼륨을 계산, 그래서 서버 throttles 자체: max_searches_per_hour (과태 60)와 폭발적인 CAPTCHA 재사용 대기시간.
• Google CAPTCHA는 더 이상 전화를 종료하지 않습니다. Google은 공유 cooldown에 간다. 같은 쿼리는 다음 엔진에 의해 답변됩니다 search_engines] (DuckDuckGo, Brave, Bing 및 기본적으로 자체 호스팅 SearXNG). data.engine] 답변 및 data.attempts 목록은 모든 시도입니다. 눈에 띄는 ([T6]]) 모드의 도전 창 화면에 왼쪽 그래서 당신은 할 수 있습니다 자신을 해결; last_captcha_at 과 engine_cooldowns_s

chrome-web-mcp

日本語版 README

Supported OS: Linux and macOS. The macOS port uses native Chrome (visible or --headless=new) and does not require X11. Windows is not supported. See docs/macos.md for macOS setup, project-local Chrome for Testing, and runtime details.

[!CAUTION] One browser at a time per profile — several MCP client processes share it.

• Normal use never trips the limiter: pace_warning fires only at 15+ searches per minute. Sequential or lightly-parallel use stays far below it.
• A warning is advisory, not a block: searches keep running. But Google counts total volume too, so the server throttles itself: max_searches_per_hour (default 60) and an exponential CAPTCHA cooldown.
• A Google CAPTCHA no longer ends the call. Google goes on a shared cooldown and the same query is answered by the next engine in search_engines (DuckDuckGo, Brave, Bing, and optionally a self-hosted SearXNG by default). data.engine reports who answered and data.attempts lists every attempt. In visible (xephyr) mode the challenge window is left on screen so you can solve it yourself; last_captcha_at and engine_cooldowns_s in health_check show the current state. Recovery is worth waiting for: sustained barrages end in CAPTCHA regardless of pacing, so if every engine is cooling down, wait a few minutes and retry.
• opencode + subagents: SAFE. All agents share one server process and one browser. Concurrent searches are pooled in a shared query queue (per-process lock + SQLite pacing) and executed sequentially — verified with 3 simultaneous subagents and 35 rapid searches, no CAPTCHA.
• Separate processes share one browser: the first process to claim the persistent profile owns Chrome/Xvfb and publishes its CDP endpoint; later processes attach to that browser (each keeps its own tabs), so N sessions cost one ~600 MB browser tree instead of N. If the registry file is missing or unusable, a process with a busy profile still falls back to its own throwaway profile exactly as before (profile_shared_fallback: true). Stagger starts by seconds or raise CW_MIN_DELAY / CW_MAX_DELAY.

A stdio Model Context Protocol server that exposes focused browser tools:

• google_search — Google search through a JavaScript-rendered Chrome instance, with automatic fallback to other engines when Google challenges.
• fetch_url — JavaScript-rendered readable text extraction for public HTTP(S) URLs.
• health_check — display, browser, queue, CAPTCHA, profile, engine, and idle release status.

The server is designed to be configured by any MCP client that can launch a stdio command.

Features

• JS-rendered Google search + public URL fetch through real Chrome. Linux uses Xephyr/Xvfb; macOS uses native visible Chrome or native --headless=new.