stealth-browser-mcp

Automate browser interactions on WAF-protected sites using anti-detection stealth patches.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/ShaggyD/agent-toolkit --skill stealth-browser-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stealth-browser-mcp
Source: https://github.com/ShaggyD/agent-toolkit/tree/main/mcp/stealth-browser
Command: npx skills add https://github.com/ShaggyD/agent-toolkit --skill stealth-browser-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp, agent-browser, and includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill solves the issue of headless browser automation being blocked by WAFs like Cloudflare, LinkedIn, and Indeed, which detect and reject standard headless Chrome sessions.

Core Features & Use Cases

  • Anti-Detection Automation: Uses stealth extensions and Chrome flags to mask headless browser identity, patching fingerprint vectors like navigator.webdriver and screen metrics.
  • Full Browser Control: Provides tools for navigation, element interaction, JavaScript evaluation, and screenshot capture within a persistent daemon session.
  • Use Case: Scrape job listings from LinkedIn or search results from protected portals without triggering CAPTCHAs or access restrictions.

Quick Start

Use the stealth browser to navigate to the target URL and extract the page text content.

Frequently Asked Questions about stealth-browser-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bypass Cloudflare WAF when web scraping with a headless browser?

Bypass Cloudflare WAF during web scraping by using anti-detection stealth patches that mask headless browser fingerprints, such as navigator.webdriver and screen metrics. This prevents standard headless Chrome sessions from being detected and blocked by WAFs.

Why does headless browser automation get blocked by sites like LinkedIn and Indeed?

Headless browser automation gets blocked because WAFs detect standard Chrome fingerprint vectors like navigator.webdriver. Anti-detection stealth patches mask these vectors, allowing reliable interaction with complex web applications without triggering CAPTCHAs or access restrictions.

Do I need agent-browser and Chromium installed to bypass bot detection?

Yes, bypassing bot detection requires the agent-browser CLI and Chromium to be installed on the host system. These dependencies provide the persistent daemon session needed for navigation, element interaction, and JavaScript evaluation with stealth patches.

Can I scrape job listings from protected portals without triggering CAPTCHAs?

Scrape job listings from protected portals without triggering CAPTCHAs by using stealth extensions and Chrome flags to mask headless browser identity. This approach patches fingerprint vectors to ensure reliable web scraping on WAF-protected sites.

Does agent-browser support JavaScript evaluation and screenshots in a persistent session?

Yes, agent-browser supports JavaScript evaluation and screenshot capture within a persistent daemon session. It provides full browser control for navigation and element interaction while applying anti-detection stealth patches to bypass WAFs.

What are the limitations of using stealth patches for web scraping automation?

Stealth patches for web scraping mask headless browser fingerprints but require the agent-browser CLI and Chromium on the host system. Complex WAF-protected sites may still update detection vectors, so persistent daemon sessions must balance anti-detection reliability with target site constraints.