Skip to main content
Glama
mysleekdesigns

CrawlForge MCP Server

stealth_mode

Bypass Cloudflare, Datadome, or CAPTCHA blocks by rendering pages in a real browser with randomized fingerprints and human-like behavior when normal scraping fails.

Instructions

Use this when a site blocks normal scraping - Cloudflare, Datadome, or other bot-detection systems. Renders in a real browser with randomized fingerprints, human behavior simulation, WebRTC/canvas spoofing - Camoufox (Firefox) when it is installed, Chromium otherwise, and the result names the one that ran. operation:"scrape" is the one-shot path: it creates a context, navigates, returns the requested formats and tears down. The create_context -> create_page -> cleanup operations remain for multi-step work. operation:"configure" only validates a stealthConfig and returns it with the defaults filled in - it stores nothing, so pass stealthConfig on each scrape or create_context call that should use it. robots.txt is respected on every navigation. Not a first choice: try scrape first and switch here after a 403/429/CAPTCHA/challenge page or an empty shell. Cost: 5 credits per browser operation; configure, get_stats and cleanup cost 1. Example: stealth_mode({operation:"scrape", url:"https://example.com", formats:["markdown","links"]})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to scrape — required for operation:"scrape"
engineNoBrowser engine: "auto" (default — camoufox when it is installed, Chromium otherwise, and the result says which), "camoufox" (Firefox-based, higher anti-detect score; fails if not installed), or "chromium" ("playwright" is the same engine under its old name)auto
formatsNoFormats to return from operation:"scrape" (default: ["markdown"]). "screenshot" returns a crawlforge://screenshot/{id} resource URI.
verboseNoReturn the full generated fingerprint from create_context instead of a summary
wait_forNoExtra wait after page load, in ms — for content that renders after DOMContentLoaded
contextIdNoBrowser context ID for page operations
operationNoStealth operation to perform. scrape: render one URL and return the formats. configure: validate stealthConfig and return it with defaults filled in; nothing is stored. create_context / create_page: a context to open pages in. get_stats: this server process's open contexts, browser and proxy state. cleanup: close the browser and every context.configure
urlToTestNoURL to navigate to when creating a page
redact_piiNoRedact personal data from the text this call returns, before it reaches your context window. true means the free regex pass over EMAIL, PHONE, FINANCIAL and SECRET. The result carries redaction:{entities,count}. Default: off
stealthConfigNoStealth browser configuration with anti-detection settings. Applies to the call it is passed on and is not remembered. Chromium applies customUserAgent, customViewport, locale and timezone per call. On camoufox customUserAgent and customViewport are not applied, locale is fixed when the browser launches (run operation:"cleanup" first to change it), and behind a proxy locale and timezone come from the exit IP; each of these is reported in `warnings`.
respect_robotsNoRespect the target site's robots.txt (default: true). Setting this to false is honoured, returns a warning in the response, and is recorded against your API key — it is your decision, not a silent default.
max_inline_charsNoLargest result to return inline, in characters of its JSON. Over it, the call returns a preview plus a result_handle for read_result instead of the whole result (default 40,000; env CRAWLFORGE_MAX_INLINE_CHARS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv6.18.1
    • changedInput schema / properties / operation / description
      Previous value: -"Stealth operation to perform"New value: +"Stealth operation to perform. scrape: render one URL and return the formats. configure: validate stealthConfig and return it with defaults filled in; nothing is stored. create_context / create_page: a context to open pages in. get_stats: this server process's open contexts, browser and proxy state. cleanup: close the browser and every context."
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "scrape",
      -  "configure",
      -  "enable",
      -  "disable",
      -  "create_context",
      -  "create_page",
      -  "get_stats",
      -  "cleanup"
      -]New value: +[
      +  "scrape",
      +  "configure",
      +  "create_context",
      +  "create_page",
      +  "get_stats",
      +  "cleanup"
      +]
    • changedInput schema / properties / stealthConfig / description
      Previous value: -"Stealth browser configuration with anti-detection settings"New value: +"Stealth browser configuration with anti-detection settings. Applies to the call it is passed on and is not remembered. Chromium applies customUserAgent, customViewport, locale and timezone per call. On camoufox customUserAgent and customViewport are not applied, locale is fixed when the browser launches (run operation:\"cleanup\" first to change it), and behind a proxy locale and timezone come from the exit IP; each of these is reported in `warnings`."
    • changedInput schema / properties / stealthConfig / properties / proxyRotation / description
      Previous value: -"Route the browser through your own proxies. Each entry is a proxy URL — \"http://user:pass@host:port\" (percent-encode a password containing @ : or /), or a bare \"host:port\" for an unauthenticated HTTP proxy; http, https, socks4 and socks5 are accepted. rotationInterval is the minimum ms on one proxy before the list advances. Cloudflare scores the IP before it serves a challenge, so a residential proxy is what gets past a block that no fingerprint fixes. CrawlForge supplies no proxies."New value: +"Route the browser through your own proxies. Each entry is a proxy URL — \"http://user:pass@host:port\" (percent-encode a password containing @ : or /), or a bare \"host:port\" for an unauthenticated HTTP proxy; http, https, socks4 and socks5 are accepted. rotationInterval is the minimum ms on one proxy before the list advances. Cloudflare scores the IP before it serves a challenge, so a residential proxy is what gets past a block that no fingerprint fixes. Requires the Chromium engine: refused on camoufox (including \"auto\" when it resolves to camoufox), which shares one launch-time proxy across calls. CrawlForge supplies no proxies."
  2. Changed4 schema fields changedv6.8.0
    • changedInput schema / properties / engine / default
      Previous value: -"playwright"New value: +"auto"
    • changedInput schema / properties / engine / description
      Previous value: -"Browser engine: \"playwright\" (Chromium, default) or \"camoufox\" (Firefox-based, higher anti-detect score — install with npm install camoufox)"New value: +"Browser engine: \"auto\" (default — camoufox when it is installed, Chromium otherwise, and the result says which), \"camoufox\" (Firefox-based, higher anti-detect score; fails if not installed), or \"chromium\" (\"playwright\" is the same engine under its old name)"
    • changedInput schema / properties / engine / enum
      Previous value: -[
      -  "playwright",
      -  "camoufox"
      -]New value: +[
      +  "auto",
      +  "chromium",
      +  "camoufox",
      +  "playwright"
      +]
    • addedInput schema / properties / stealthConfig / properties / proxyRotation / description
      Added value: +"Route the browser through your own proxies. Each entry is a proxy URL — \"http://user:pass@host:port\" (percent-encode a password containing @ : or /), or a bare \"host:port\" for an unauthenticated HTTP proxy; http, https, socks4 and socks5 are accepted. rotationInterval is the minimum ms on one proxy before the list advances. Cloudflare scores the IP before it serves a challenge, so a residential proxy is what gets past a block that no fingerprint fixes. CrawlForge supplies no proxies."
  3. Changed8 schema fields changedv6.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / max_inline_chars
      Added value: +{
      +  "description": "Largest result to return inline, in characters of its JSON. Over it, the call returns a preview plus a result_handle for read_result instead of the whole result (default 40,000; env CRAWLFORGE_MAX_INLINE_CHARS)",
      +  "maximum": 10000000,
      +  "minimum": 1000,
      +  "type": "integer"
      +}
    • addedInput schema / properties / redact_pii
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "properties": {
      +        "entities": {
      +          "description": "Which classes to redact, case-insensitive: EMAIL, PHONE, FINANCIAL, SECRET, plus PERSON and LOCATION when mode is \"model\". Omitted or empty means all four regex classes (and both model classes in \"model\" mode). An unknown name, or a model-only name without mode:\"model\", is rejected",
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "mode": {
      +          "description": "\"fast\" (default) is regex only and free; \"model\" adds an Ollama NER pass for PERSON and LOCATION (+3 credits once per call)",
      +          "enum": [
      +            "fast",
      +            "model"
      +          ],
      +          "type": "string"
      +        },
      +        "replace_style": {
      +          "description": "\"tag\" (default) writes <EMAIL>, \"mask\" writes [REDACTED], \"remove\" deletes the value",
      +          "enum": [
      +            "tag",
      +            "mask",
      +            "remove"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  ],
      +  "description": "Redact personal data from the text this call returns, before it reaches your context window. true means the free regex pass over EMAIL, PHONE, FINANCIAL and SECRET. The result carries redaction:{entities,count}. Default: off"
      +}
    • removedInput schema / properties / stealthConfig / additionalProperties
      Removed value: -false
    • removedInput schema / properties / stealthConfig / properties / antiDetection / additionalProperties
      Removed value: -false
    • removedInput schema / properties / stealthConfig / properties / customViewport / additionalProperties
      Removed value: -false
    • removedInput schema / properties / stealthConfig / properties / fingerprinting / additionalProperties
      Removed value: -false
    • removedInput schema / properties / stealthConfig / properties / proxyRotation / additionalProperties
      Removed value: -false
  4. Changed6 schema fields changedv5.4.0
    • addedInput schema / properties / formats
      Added value: +{
      +  "default": [
      +    "markdown"
      +  ],
      +  "description": "Formats to return from operation:\"scrape\" (default: [\"markdown\"]). \"screenshot\" returns a crawlforge://screenshot/{id} resource URI.",
      +  "items": {
      +    "enum": [
      +      "markdown",
      +      "html",
      +      "text",
      +      "links",
      +      "metadata",
      +      "screenshot"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "configure",
      -  "enable",
      -  "disable",
      -  "create_context",
      -  "create_page",
      -  "get_stats",
      -  "cleanup"
      -]New value: +[
      +  "scrape",
      +  "configure",
      +  "enable",
      +  "disable",
      +  "create_context",
      +  "create_page",
      +  "get_stats",
      +  "cleanup"
      +]
    • addedInput schema / properties / respect_robots
      Added value: +{
      +  "description": "Respect the target site's robots.txt (default: true). Setting this to false is honoured, returns a warning in the response, and is recorded against your API key — it is your decision, not a silent default.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "URL to scrape — required for operation:\"scrape\"",
      +  "format": "uri",
      +  "type": "string"
      +}
    • addedInput schema / properties / verbose
      Added value: +{
      +  "default": false,
      +  "description": "Return the full generated fingerprint from create_context instead of a summary",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / wait_for
      Added value: +{
      +  "description": "Extra wait after page load, in ms — for content that renders after DOMContentLoaded",
      +  "maximum": 30000,
      +  "minimum": 0,
      +  "type": "number"
      +}
  5. Changed1 schema field changedv5.0.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. First observedv4.10.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses cost (5 credits per browser op; 1 for configure/get_stats/cleanup), that robots.txt is respected on every navigation, that configure stores nothing so stealthConfig must be re-passed, and which engine ran. Annotations only cover the safety/idempotency profile, so this context is genuinely additive.

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?

Front-loads the trigger condition and the anti-detection value before the operational details, and every sentence carries information. It is dense and long, but not padded; the cost and example are the only borderline lines.

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

Completeness4/5

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

For a 12-param, nested-object tool with no output schema, it covers trigger, alternatives, cost, engine selection, config persistence, and robots behavior. It partially signals return content (engine name, redaction counts) but does not fully characterize output shape, which is acceptable given the depth provided.

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 coverage is 100%, so the baseline is 3. The description adds the operation lifecycle framing (scrape tears down; create_context/create_page/cleanup for multi-step; configure validates and stores nothing), which clarifies how parameters interact across calls beyond the enum's own text.

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?

States a specific verb+resource+scope: renders in a real browser with randomized fingerprints when a site blocks normal scraping, naming the anti-detect stack (Camoufox/Chromium). It explicitly distinguishes itself from the sibling 'scrape' tool, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (site blocks: Cloudflare, Datadome, bot-detection), when-not ('Not a first choice: try scrape first'), and the trigger to switch (403/429/CAPTCHA/challenge page or empty shell). It also maps operations to workflows: scrape as the one-shot path vs create_context/create_page/cleanup for multi-step work.

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