Scrapling MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_openA | Open a reusable stealthy browser session. Pass per-request options to |
| browser_save_stateB | Save browser cookies, local storage and IndexedDB as Playwright-compatible JSON. Excludes sessionStorage. |
| browser_load_stateA | Replace browser cookies, local storage and IndexedDB from a Playwright-compatible JSON file. Leaves sessionStorage and open tabs unchanged. Fetch or reload pages to use the restored login. |
| open_request_sessionA | Open a reusable HTTP session for |
| close_sessionB | Close a session and free its resources. |
| list_sessionsB | List registered sessions, their status, and effective settings. |
| make_requestB | Make an HTTP request without JavaScript. Suitable for low-to-mid protection. |
| browser_fetch_onceB | Fetch a page with a stealth browser and JavaScript rendering. |
| browser_fetchB | Fetch a URL in an open stealthy browser session. Options apply only to this request. |
| session_make_requestB | Make an HTTP request using the session's cookies, connections, impersonation, and proxy. Options apply to this request. |
| browser_extractA | Read the current page or one element as snapshot, HTML, Markdown, or text without navigating. Return plain text; snapshot search keeps refs, ancestor paths and three lines of nearby context. |
| browser_actionsA | Run mouse, field, key, dialog, and wait actions in order; return plain text without a snapshot. Stop on the first error, identifying its action; partial effects remain. No retries. Element mouse targets auto-wait and scroll into view; coordinates and wheel do not wait for navigation or scrolling. Cancelled/timed-out clicks attempt button release. Load waits observe the current document, not future navigation. |
| browser_evaluateA | Run JavaScript on the current page, await promises, and return JSON text without a snapshot. Return JSON-compatible values; null/undefined become null. Script effects are not undone on failure. Cancellation stops waiting, but may not stop the script. |
| browser_network_requestsA | List completed requests across page changes, with IDs and pagination. Recording starts when the browser session opens. |
| browser_network_requestA | Read a complete saved request part without resending it, with structured data and availability notes. |
| browser_screenshotA | Capture the current page or one element without navigating; return the image and current URL. Element capture waits and scrolls into view. Use browser_actions for other waits before capture. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
The set contains several close pairs whose boundaries require careful reading of descriptions: make_request vs session_make_request, browser_fetch vs browser_fetch_once, and browser_network_requests vs browser_network_request. The distinctions exist (stateless vs session-bound, one-off vs persistent, list vs detail), but an agent can easily misselect without parsing the long descriptions.
There are two coherent families: browser_* prefixed tools and session/verb-first tools (open_request_session, close_session, list_sessions, session_make_request, make_request). Within each family it is readable, but the mixed conventions across the set (browser_open vs open_request_session, bare make_request vs session_make_request) create inconsistency.
16 tools is borderline heavy for the surface. Many are justified (fetch variants, network inspection), but the fetch/request pairs (browser_fetch vs browser_fetch_once, make_request vs session_make_request) inflate the count and add selection burden without adding fundamentally new capability.
The surface covers the full scraping lifecycle: session lifecycle (open/close/list), state save/load, multiple fetch/request modes, extraction, actions, evaluation, network inspection, and screenshots. Minor gaps exist (no explicit browser teardown distinct from close_session, no cookie-specific tool), but the core workflow is well covered.