ScorchCrawl FAQs

Question 1

Does ScorchCrawl ensure the security of sensitive user data?

Accepted Answer

Yes, when running in `stdio` mode, ScorchCrawl keeps per-user secrets, such as GitHub tokens, local to the client environment, enhancing data privacy and security.

Question 2

Is ScorchCrawl a standalone web scraping engine?

Accepted Answer

No, ScorchCrawl acts as a crucial bridge or proxy. It connects AI clients to the separate `scorchcrawl` core scraping engine, which performs the actual web scraping and data extraction.

Question 3

Which AI clients are supported by ScorchCrawl?

Accepted Answer

ScorchCrawl supports any Model Context Protocol (MCP) clients, including popular AI assistants and tools like VS Code Copilot, Claude Desktop, and other compatible clients.

Question 4

What is ScorchCrawl?

Accepted Answer

ScorchCrawl is an MCP proxy/server that bridges AI clients like VS Code Copilot and Claude Desktop to a powerful web scraping engine, enabling AI-driven data collection and data extraction.

Question 5

How can I deploy ScorchCrawl?

Accepted Answer

ScorchCrawl offers flexible deployment options: as a local `stdio` proxy via npm, a remote HTTP `SSE` server, or a full-stack solution with Docker Compose including all supporting services.

ScorchCrawl

ScorchCrawl

Key Features

Use Cases

Key Features

Use Cases