Introduction

Overview

The ScrapeGraphAI MCP Server is a hosted Model Context Protocol (MCP) server that connects Large Language Models (LLMs) to the ScrapeGraphAI API. It lets AI assistants like Cursor, Claude, and Codex scrape, extract, search, crawl, and schedule page monitors through natural language, without writing any code.

What is MCP?

The Model Context Protocol (MCP) is a standardized way for AI assistants to access external tools and data sources. By connecting the ScrapeGraphAI MCP Server, your AI assistant gains access to the full v2 API surface as callable tools.

Key Features

20 Tools

Scrape, extract, search, crawl, schedule page monitors, and inspect credits and request history

Hosted, No Install

One HTTPS endpoint — nothing to install, run, or keep up to date

Google or API Key

Universal Compatibility

Works with Cursor, Claude Desktop, Claude Code, Codex, and any MCP-compatible client

Endpoint

https://mcp.scrapegraphai.com/mcp

The server speaks Streamable HTTP. The legacy HTTP+SSE transport is not supported — if your client offers a transport choice, pick HTTP (not SSE). Individual tool calls run up to 60 seconds; use the async crawl_* and monitor_* tools for longer jobs.

Quick Start

Choose how to sign in

Choose your client

Pick your assistant: Cursor, Claude Desktop, Claude Code, or Codex.

Add the server

Follow the setup guide for your client to register the sgai server and authenticate.

Verify

Ask your assistant to run the credits tool. A balance response confirms the connection works end to end.

Setup Guides

Cursor Setup

Configure ScrapeGraph MCP in Cursor

Claude Desktop Setup

Configure ScrapeGraph MCP in Claude Desktop

Claude Code Setup

Configure ScrapeGraph MCP in Claude Code

Codex Setup

Configure ScrapeGraph MCP in Codex

Authentication

Add the server without any credentials. On first connection the client discovers the OAuth metadata, registers itself, and opens the ScrapeGraphAI login page in your browser.

{
  "mcpServers": {
    "sgai": {
      "url": "https://mcp.scrapegraphai.com/mcp"
    }
  }
}

Restart your MCP client

Restart the client after saving its MCP configuration so that it loads the new sgai server.

Start authentication

Run /mcp in your client, select sgai, and choose the option to authenticate. In Claude Code and Codex you can also start the flow from the terminal with claude mcp login sgai or codex mcp login sgai.

Continue with Google

In the browser window that opens, select Continue with Google and use the Google account associated with your ScrapeGraphAI account.

Confirm the connection

Return to your client after you see Authentication successful. Connected to sgai. The server is ready to use.

The flow is standard OAuth 2.1 with PKCE (S256) and dynamic client registration, requesting the mcp:use scope. Tools run against the workspace tied to the account you signed in with.

Authenticate with an API key

Set your API key in the SGAI_API_KEY environment variable and reference it from the client config:

{
  "mcpServers": {
    "sgai": {
      "url": "https://mcp.scrapegraphai.com/mcp",
      "bearer_token_env_var": "SGAI_API_KEY"
    }
  }
}

Clients that send raw headers instead can pass the key as Authorization: Bearer sgai-..., SGAI-APIKEY, or X-API-Key. Any request carrying an API key skips the OAuth flow entirely.

Verify the connection

Ask your assistant to run the credits tool. A successful balance response confirms that both authentication and tool execution are working.

Available Tools

Every tool maps to a v2 API endpoint and runs against the workspace you authenticated with.

Scraping

Tool	Description
scrape	Fetch a URL as markdown (default), html, screenshot, branding, links, images, summary, or json — `POST /api/scrape`
extract	AI-powered structured extraction from a URL, raw HTML, or markdown — `POST /api/extract`
search	Search the web and extract structured data from the results (1–20 results, default 3) — `POST /api/search`

Crawling

Tool	Description
crawl_start	Start an async multi-page crawl (default 50 pages, depth 2; max 1000 pages) — `POST /api/crawl`
crawl_get	Get crawl status and pages — `GET /api/crawl/:id`
crawl_pages	Get paginated crawl pages (default 50 per page, max 100) — `GET /api/crawl/:id/pages`
crawl_stop	Stop a running crawl — `POST /api/crawl/:id/stop`
crawl_resume	Resume a paused crawl — `POST /api/crawl/:id/resume`
crawl_delete	Delete a crawl — `DELETE /api/crawl/:id`

Monitors

Tool	Description
monitor_create	Schedule a page-change monitor with a cron expression or shorthand (e.g. `1h`) — `POST /api/monitor`
monitor_list	List all monitors — `GET /api/monitor`
monitor_get	Get monitor details — `GET /api/monitor/:id`
monitor_update	Update a monitor’s name, interval, formats, or webhook — `PATCH /api/monitor/:id`
monitor_pause	Pause a running monitor — `POST /api/monitor/:id/pause`
monitor_resume	Resume a paused monitor — `POST /api/monitor/:id/resume`
monitor_delete	Delete a monitor — `DELETE /api/monitor/:id`
monitor_activity	Poll a monitor’s tick history (default 20 per page, max 100) — `GET /api/monitor/:id/activity`

Account

Tool	Description
credits	Check your credit balance — `GET /api/credits`
history_list	Browse request history, filterable by service — `GET /api/history`
history_get	Get a single request history entry — `GET /api/history/:id`

Coming from the legacy scrapegraph-mcp package? The hosted server exposes the v2 API under its canonical names:

Legacy tool	Now
`smartscraper`	`extract`
`searchscraper`	`search`
`markdownify`	`scrape` with `formats: ["markdown"]`
`smartcrawler_initiate`	`crawl_start`
`smartcrawler_fetch_results`	`crawl_get`, or `crawl_pages` for pagination
`sgai_history`	`history_list`
`generate_schema`	Removed — pass a JSON Schema directly via the `schema` parameter on `extract` and `search`
`sitemap`, `agentic_scrapper`	No direct equivalent on the hosted server

Use Cases

Research & Analysis — Extract data from multiple sources for research
Content Aggregation — Collect and structure content from websites
Market Intelligence — Monitor competitors and track page changes over time
Lead Generation — Extract contact information and company data
Data Collection — Build datasets from web sources

Next Steps

Set up your client: Cursor, Claude Desktop, Claude Code, or Codex
Browse the v2 API reference for full parameter documentation on every tool

Ready to Start?

Choose your client and start scraping with AI!

Get Started

Services

Official SDKs

LLM SDKs

Frameworks

Personal AI Agents

No-code

Contribute

Overview

What is MCP?

Key Features

20 Tools

Hosted, No Install

Google or API Key

Universal Compatibility

Endpoint

Quick Start

Setup Guides

Cursor Setup

Claude Desktop Setup

Claude Code Setup

Codex Setup

Authentication

Authenticate with an API key

Verify the connection

Available Tools

Scraping

Crawling

Monitors

Account

Use Cases

Next Steps

Ready to Start?

​Overview

​What is MCP?

​Key Features

20 Tools

Hosted, No Install

Google or API Key

Universal Compatibility

​Endpoint

​Quick Start

​Setup Guides

Cursor Setup

Claude Desktop Setup

Claude Code Setup

Codex Setup

​Authentication

​Sign in with Google (recommended)

​Authenticate with an API key

​Verify the connection

​Available Tools

​Scraping

​Crawling

​Monitors

​Account

​Use Cases

​Next Steps

Ready to Start?

Overview

What is MCP?

Key Features

Endpoint

Quick Start

Setup Guides

Authentication

Sign in with Google (recommended)

Authenticate with an API key

Verify the connection

Available Tools

Scraping

Crawling

Monitors

Account

Use Cases

Next Steps