Scrapling MCP Server

Open browser

browser_open

Starts a reusable stealth browser session with configurable proxy, cookies, locale, and anti-detection options, then pass per-request settings to browser_fetch for live web extraction.

Instructions

Open a reusable stealthy browser session. Pass per-request options to browser_fetch.

Input Schema

Name	Required	Description
`proxy`	No	Proxy URL, or dictionary with server and optional username/password.
`locale`	No	Browser language, Accept-Language, and formatting locale; system default if omitted.
`cdp_url`	No	Connect to an existing Chromium browser over CDP in a new context; launch settings do not apply.
`cookies`	No	Initial cookies as Playwright cookie dictionaries.
`headless`	No	Hide the browser window.
`useragent`	No	User-Agent override; otherwise generated in headless mode, native in headful mode.
`session_id`	No	Custom ID; a random 12-character hex ID if omitted.
`allow_webgl`	No	Enable WebGL; disabling it can trigger bot detection.
`hide_canvas`	No	Add noise to canvas operations.
`real_chrome`	No	Use locally installed Chrome.
`timezone_id`	No	Browser timezone; uses the system timezone if omitted.
`block_webrtc`	No	Disable non-proxied WebRTC UDP to reduce IP leaks.
`additional_args`	No	Browser context options that override Scrapling settings.
`executable_path`	No	Absolute Chromium-compatible executable path; overrides the server default.

Output Schema

Name	Required	Description	Default
`session_id`	Yes	The unique identifier of the session.
`session_type`	Yes	The type of the session: 'stealthy' or 'static'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds the meaningful traits 'stealthy' and 'reusable', but says nothing about session lifetime, cleanup requirements (close_session), or resource persistence, leaving important behavioral context unstated.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and resource, with zero filler. The downstream-tool hint is placed immediately after the core purpose.

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

Completeness3/5

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

Output schema exists, so return values need not be described. However, for a 14-parameter session opener, the description omits how sessions are reused across calls, whether they must be closed, and what happens if a session_id already exists — leaving the lifecycle under-specified.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds one genuinely useful routing signal: per-request options belong on browser_fetch, clarifying the division of labor between session creation and request execution beyond what the schema alone conveys.

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

Purpose4/5

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

States a specific verb and resource — open a reusable stealthy browser session — and names a downstream sibling (browser_fetch). It does not distinguish itself from other session-creating siblings such as open_request_session or browser_fetch_once, so differentiation is incomplete.

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

Usage Guidelines3/5

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

The line 'Pass per-request options to browser_fetch' implies the session is a container for later fetch calls, but it never says when to choose this over open_request_session or browser_fetch_once. Usage is inferable but not explicitly guided.

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

Deploy Server