scrapegraphai

The ScrapeGraphAI MCP Server is a production-ready Model Context Protocol (MCP) server that connects Large Language Models (LLMs) to the ScrapeGraph AI API.

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

  • Extract: Extract structured data from a webpage using AI (API v2 POST /extract).
  • Search: AI-powered web search with structured data extraction (API v2 POST /search).
  • Crawl Start: Start an asynchronous multi-page crawl (API v2 POST /crawl). Poll crawl_get_status with the returned id.

What data it sees

Do you need an account

An API key from the service settings is required

The ScrapeGraphAI MCP Server is a production-ready Model Context Protocol (MCP) server that connects Large Language Models (LLMs) to the ScrapeGraph AI API. It enables AI assistants like Claude and Cursor to perform AI-powered web scraping, research, and crawling directly through natural language interactions.

How to connect

How to connect scrapegraphai to Claude

The server address to paste into Claude settings:

https://sgai--scrapegraphai-inc.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect scrapegraphai to ChatGPT

The server address to paste into ChatGPT settings:

https://sgai--scrapegraphai-inc.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect scrapegraphai to Cursor

The server address to paste into Cursor settings:

https://sgai--scrapegraphai-inc.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (17)

Raw names from tools/list. Only developers need these.

extractExtract structured data from a webpage using AI (API v2 POST /extract).
searchAI-powered web search with structured data extraction (API v2 POST /search).
crawl_startStart an asynchronous multi-page crawl (API v2 POST /crawl). Poll crawl_get_status with the returned id.
crawl_get_statusRetrieve the results of an asynchronous SmartCrawler operation. This tool fetches the results from a previously initiated crawling operation using the request_id. The crawl request processes asynchronously in the background. Keep polling this endpoint until the status field indicates 'completed'. While processing, you'll receive status updates. Read-only operation that safely retrieves results without side effects.
crawl_stopStop a running crawl job (API v2 POST /crawl/:id/stop).
crawl_resumeResume a stopped crawl job (API v2 POST /crawl/:id/resume).
creditsReturn remaining API credits (API v2 GET /credits).
historyList recent API requests (API v2 GET /history). v2 accepts page/limit/service. The legacy endpoint/offset params are kept as aliases and translated client-side (endpoint -> service, offset -> page when it divides limit). status filtering was removed in v2.
monitor_createCreate a scheduled monitor job (API v2 POST /monitor). The v2 API expects a `formats` array. This tool wraps `prompt` (+ optional `output_schema`) into a `{type: "json", ...}` format entry for you.
schemaGenerate or augment a JSON Schema from a natural-language prompt (API v2 POST /schema).
monitor_listList monitors (API v2 GET /monitor).
monitor_getGet one monitor by id (API v2 GET /monitor/:id).
monitor_pausePause a monitor (API v2 POST /monitor/:id/pause).
monitor_resumeResume a paused monitor (API v2 POST /monitor/:id/resume).
monitor_deleteDelete a monitor (API v2 DELETE /monitor/:id).
monitor_activityPoll per-run tick history for a monitor (API v2 GET /monitor/:id/activity). Returns the ticks produced on each scheduled run (`id`, `createdAt`, `status`, `changed`, `elapsedMs`, `diffs`) plus `nextCursor` when more results are available. Mirrors `sgai.monitor.activity()` in scrapegraph-py v2.
scrapeFetch page content (API v2 POST /scrape).