Stealth Browser MCP Server

A MCP Server that provides browser access through playwright with "stealth mode" enabled. That is what the stealth browser mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP (Model Context Protocol) server that provides stealth browser capabilities using Playwright with anti-detection techniques. This server allows MCP clients to navigate to websites and take screenshots while evading common bot detection systems.

• Stealth Mode — Uses puppeteer-extra-plugin-stealth with playwright-extra to bypass bot detections
• Modifies browser fingerprints to appear as regular user traffic
• Handles WebGL, canvas, font, plugin and other browser fingerprinting techniques
• Screenshot Tool — Take full-page or element-specific screenshots of any website
• Supports both headless (default) and visible browser modes
• MCP Integration — Exposes browser capabilities via Model Context Protocol

The tools it exposes

The server publishes 1 tool. What each one is for:

• screenshot — Parameters: - url (string, required): The URL to navigate to - fullPage (boolean, optional, default: true): Whether to capture the entire page -

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Stealth Browser's toolset — screenshot — is a fair guide to whether it matches your workflow. It is maintained by newbeb; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Stealth Browser's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.