DocumentationDeveloper ToolsScrapeless MCPConfiguration

Configuration

Beyond the API token, you can customize how Scrapeless MCP runs each session. Options are supplied as environment variables (Stdio) or HTTP headers (Streamable HTTP) — the two forms map one-to-one.

Session options

Stdio (Env Var)Streamable HTTP (Header)Description
SCRAPELESS_KEYx-api-tokenRequired. Your Scrapeless API token.
BROWSER_PROFILE_IDx-browser-profile-idReusable browser profile ID for session continuity across runs.
BROWSER_PROFILE_PERSISTx-browser-profile-persistEnables persistent storage for cookies, local storage, and other browser state.
BROWSER_SESSION_TTLx-browser-session-ttlMaximum session timeout in seconds. The session expires after this duration of inactivity.

Examples

Stdio — persistent profile with a 5-minute TTL

{
  "mcpServers": {
    "Scrapeless MCP Server": {
      "command": "npx",
      "args": ["-y", "scrapeless-mcp-server"],
      "env": {
        "SCRAPELESS_KEY": "YOUR_SCRAPELESS_KEY",
        "BROWSER_PROFILE_ID": "my-profile",
        "BROWSER_PROFILE_PERSIST": "true",
        "BROWSER_SESSION_TTL": "300"
      }
    }
  }
}

Streamable HTTP — same options as headers

{
  "mcpServers": {
    "Scrapeless MCP Server": {
      "type": "streamable-http",
      "url": "https://api.scrapeless.com/mcp",
      "headers": {
        "x-api-token": "YOUR_SCRAPELESS_KEY",
        "x-browser-profile-id": "my-profile",
        "x-browser-profile-persist": "true",
        "x-browser-session-ttl": "300"
      }
    }
  }
}

Tips

  • Profiles let an agent keep a logged-in session across multiple runs — set the same BROWSER_PROFILE_ID each time and enable persistence.
  • TTL balances cost and continuity: shorter TTLs release cloud resources sooner; longer TTLs keep a warm session available for follow-up requests.
  • Options that are omitted fall back to Scrapeless defaults, so you only need to set what you want to change.

For a full walkthrough of transports and authentication, see Authentication and Transports.