Skip to main content
Glama
RobithYusuf

mcp-stealth-chrome

by RobithYusuf
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

browser_launch

Launch a stealth Chrome browser with anti-detection features, including automatic Cloudflare and Turnstile challenge solving. Customize proxies, user agents, viewport, and reuse persistent profiles for automated browsing tasks.

Instructions

Launch stealth Chrome via nodriver. Creates persistent profile by default.

Args:
    url: initial URL to load
    headless: run without UI (many sites detect headless — prefer False)
    proxy: "http://user:pass@host:port" or "socks5://host:port"
    user_agent: override UA string
    window_width, window_height: viewport size
    persistent: reuse profile at ~/.mcp-stealth/profile
    lang: browser language
    extra_args: additional Chromium flags
    storage_state_path: load cookies/localStorage from JSON before first nav
    testing_mode: 2-5× faster startup+nav for perf/regression testing —
        disables image loading, background throttling dampers, translate,
        notifications, media autoplay. WARNING: reduces stealth — not for
        anti-bot work (sites can detect missing images as automation signal).
    auto_verify: if True (default), automatically detect Cloudflare /
        Turnstile challenges after the initial load and dispatch a
        CDP-level click on the checkbox. Caps at 2 attempts ~6s total —
        never loops. Set False to opt out.
    user_data_dir: launch Chrome against an EXISTING user profile root
        (e.g. "~/Library/Application Support/Google/Chrome"). Overrides
        persistent + the default MCP profile. The target Chrome instance
        (if any) MUST be closed first — locked profiles are detected
        upfront and refused with the lock-holder PID. Supports ~ expansion.
    profile_directory: when paired with user_data_dir, picks a sub-profile
        inside it (e.g. "Default", "Profile 21"). Without this, Chrome
        uses "Default". Helpful to drive a specific persona without
        cloning the profile. Use list_chrome_profiles to enumerate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoabout:blank
headlessNo
proxyNo
user_agentNo
window_widthNo
window_heightNo
persistentNo
langNoen-US
extra_argsNo
storage_state_pathNo
testing_modeNo
auto_verifyNo
user_data_dirNo
profile_directoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of disclosing behavior. It covers stealth modifications, persistent profile default, headless detection warning, testing_mode impacts, auto_verify behavior, and user_data_dir constraints. However, it does not describe the output behavior (e.g., returns a browser instance ID) or lifecycle aspects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose statement followed by a detailed parameter list. It is relatively long but each sentence adds value. Minor improvement could be using bullet points for readability, but it remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters, no annotations, and an output schema that is not explained, the description covers all parameters with thorough explanations, including edge cases and warnings. It provides sufficient context for an AI agent to correctly invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully explain parameters. It does so excellently: each parameter is described with context, warnings, and defaults (e.g., 'many sites detect headless — prefer False', 'caps at 2 attempts ~6s total'). This adds significant value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Launch stealth Chrome via nodriver. Creates persistent profile by default.' This clearly identifies the tool's action and resource, distinguishing it from siblings like attach_to_chrome (which attaches to existing instances) and spawn_browser.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given on when to use this tool versus alternatives. The description does not mention when to prefer browser_launch over sibling tools like spawn_browser or attach_to_chrome, nor does it provide exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RobithYusuf/mcp-stealth-chrome'

If you have feedback or need assistance with the MCP directory API, please join our Discord server