scrapeLABSCO SUMMARY
Stop and resume on a crawl is what makes a large one survivable.
A crawl that can only run to completion means any interruption — a rate limit, a bad selector spotted halfway, a credit ceiling — costs you the whole run. Being able to pause, look at the pages collected so far, and pick the job back up turns crawling into something you can supervise. The monitors are the other half: a watch that reports activity is how you track a page over time without re-scraping it on a cron and paying for the unchanged copies.
What it is
ScrapeGraphAI's hosted endpoint. Beyond one-shot scraping it covers crawls as long-running jobs and monitors as standing watches.
What you get
- scrape, extract and search for single-page work
- Crawls across their whole lifecycle — start, get, list pages, stop, resume, delete
- Monitors — create, list, get, update, pause, resume, delete, and read their activity
- Account tools for credits and history
Requirements
OAuth through Google is their recommended path; an API key as a bearer token is the alternative. Fully hosted — there is no local package.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Pulling one page apart
Scrape it, or extract the specific fields you want.
02
Crawling a site properly
Start the job, watch the pages arrive, stop and resume as needed.
03
Watching for a change
A monitor with its own activity log, rather than a repeated scrape.
04
Knowing what it costs
Credits and history from the same connection.
20 tools
Listed in project docs. Your client may show a different list.
extractsearchcrawl_startcrawl_getcrawl_pagescrawl_stopcrawl_resumecrawl_deletemonitor_createmonitor_listmonitor_getmonitor_updatemonitor_pausemonitor_resumemonitor_deletemonitor_activitycreditshistory_listhistory_getBEFORE YOU INSTALL
What to know first
Tools you get
20 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 through Google, which the vendor recommends, or an API key as a bearer token
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.scrapegraphai.com/mcpRequirements
- OAuth 2.1 through Google, which the vendor recommends, or an API key as a bearer token
