← Back to directory
S

ScrapeGraph MCP Server

Community
AI-powered web scraping and data extraction with enterprise reliability via ScrapeGraph API.
GitHub source repository ↗
★ 96 Stars Category · Dev Tools Popular Source revision 8372895aa6ea
52FMRS · D
Reliability
5/20
Security and permissions
9/20
Maintenance
12/20
Documentation
14/20
Setup experience
12/20

This MCP server offers AI-powered web scraping functionality with a rich set of tools covering scrape, extract, search, crawl, and monitor. Setup is easy but requires a paid API key. Note that tool names were renamed in v3; consult the documentation when upgrading.

Read the FMRS scoring method →

The ScrapeGraph MCP Server is a production-ready Model Context Protocol (MCP) server that provides seamless integration with the ScrapeGraph AI API. It enables language models to leverage advanced AI-powered web scraping capabilities, offering tools for scraping (multi-format), prompt-based extraction, search, async multi-page crawling (start/status/stop/resume), JSON schema generation, scheduled monitoring (create/list/get/pause/resume/delete/activity), account credits, and history. The server uses stdio transport and can be configured via environment variables (SGAI_API_KEY, SGAI_API_URL, SGAI_TIMEOUT). Note that v3 has renamed tools, e.g., smartscraper to extract, smartcrawler_initiate to crawl_start.

Tools

scrape
Scrape a webpage and output multiple formats: markdown, html, screenshot, branding, links, images, summary.
extract
Extract structured data based on a prompt, requiring website_url and user_prompt, with optional output_schema.
search
Perform a search returning up to 20 results, supporting country_search, time_range, and output_schema.
crawl_start
Start async multi-page crawl with extraction_mode: markdown, html, links, images, summary, branding, screenshot.
crawl_get_status
Get status of a crawl job; poll until status is completed.
crawl_stop
Stop an ongoing crawl job.
crawl_resume
Resume a paused crawl job.
schema
Generate or augment a JSON Schema from a prompt.
credits
Get account credits.
history
Get paginated usage history, optionally filtered by service.
monitor_create
Create a scheduled monitoring job.
monitor_list
List all monitoring jobs.
monitor_get
Get details of a specific monitoring job.
monitor_pause
Pause a monitoring job.
monitor_resume
Resume a monitoring job.
monitor_delete
Delete a monitoring job.
monitor_activity
Get paginated activity history of a monitoring job (id, createdAt, status, changed, elapsedMs, diffs).

Setup

  1. Obtain an API key from the ScrapeGraph Dashboard. 2. Quick install with Smithery: npx -y @smithery/cli install @ScrapeGraphAI/scrapegraph-mcp --client claude. 3. Or install locally: clone repo, pip install -e ., then set environment variable SGAI_API_KEY and run with scrapegraph-mcp or python -m scrapegraph_mcp.server. 4. Configure Claude Desktop or Cursor using the JSON configs provided in the README.
claude_desktop_config.json
{
  "mcpServers": {
    "scrapegraph-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "@ScrapeGraphAI/scrapegraph-mcp",
        "--config",
        "\"{\\\"scrapegraphApiKey\\\":\\\"YOUR-SGAI-API-KEY\\\"}\""
      ]
    }
  }
}

Fit and risk

Best for

  • AI assistant developers who need natural-language-driven web scraping and structured data extraction.
  • Crawler and data analysis workflows that need automated extraction from multiple pages.
  • Users who need to monitor website changes and extract information on a schedule.

Not for

  • Developers who don't need AI-assisted scraping and just want simple direct HTTP requests.
  • Users without a ScrapeGraph AI paid subscription or with limited credits, as API calls may incur costs.
  • Users needing local JavaScript rendering without using ScrapeGraph API's rendering capabilities.

Required permissions

  • Requires a ScrapeGraph API key (SGAI_API_KEY) to access ScrapeGraph services.
  • Requires network access to reach the ScrapeGraph API (default https://v2-api.scrapegraphai.com/api).
  • API key passed via environment variable or MCP config, which may involve secret management.

Risks and side effects

  • API key leakage could lead to unauthorized usage and credit loss.
  • API calls are subject to rate limiting and quota management; exceeding may incur extra costs.
  • Scraping websites may violate their terms of service or laws; use responsibly.

Troubleshooting

  1. If tools don't appear in client, check that the server starts properly and the API key is correct.
  2. If you get 401 Unauthorized, verify your API key is valid.
  3. If you get 402 Payment Required, check your account credits.
  4. If crawl doesn't return results, keep polling crawl_get_status until status is 'completed'.
  5. On Windows, use the specific command or check PATH settings.

Use cases

Convert a webpage to Markdown for easy LLM processing.
Extract all product names, prices, and ratings from an e-commerce page.
Search for recent AI developments and get a structured summary.
Crawl multiple pages of a site to map content or capture API endpoints.
Set up daily scheduled monitoring to track changes on specific data.

Supported clients

Claude DesktopFull support
CursorFull support