ScrapeGraphAI Scrapegraph Mcp
Let Claude Code or Cursor agents run AI-guided web scraping for competitor pages, pricing, and lead lists without hand-writing scrapers.
Overview
ai.smithery/ScrapeGraphAI-scrapegraph-mcp is a MCP server for the Idea phase that lets agents perform AI-powered web scraping through Smithery’s hosted ScrapeGraphAI endpoint.
What is this MCP server?
- Streamable HTTP MCP remote on Smithery with Bearer smithery_api_key auth
- ScrapeGraphAI-backed extraction aimed at enterprise-style reliability vs raw HTML fetches
- Exposes scraping tools to any MCP-compatible agent for repeatable research workflows
- GitHub source at ScrapeGraphAI/scrapegraph-mcp (catalog version 1.16.0)
- Fits competitive intel and landing-page teardowns without leaving the agent chat
- Catalog server version 1.16.0
- 1 streamable-http remote on server.smithery.ai
- 1 required secret header: Authorization Bearer smithery_api_key
Community signal: 81 GitHub stars.
What problem does it solve?
Market and competitor research stalls when every site needs a custom scraper and agents can only guess from stale training data.
Who is it for?
Solo builders doing competitor teardowns, directory mining, or pricing checks from inside Claude Code or Cursor with Smithery already configured.
Skip if: Teams that need self-hosted scrapers, strict compliance programs without reviewing ScrapeGraph’s terms, or workflows that only need a single static PDF.
What do I get? / Deliverables
Your agent can call scraping tools over MCP so research pulls live page content into structured answers you can cite in validation notes.
- Agent-callable scraping tool surface over MCP
- Live extracted web content usable in research and spec drafts
- Repeatable Smithery remote config snippet for your agent
Recommended MCP Servers
Journey fit
Solo builders most often wire scraping MCPs during opportunity research before they commit to a niche or feature set. Research is where structured extraction from live sites replaces brittle copy-paste and one-off scripts.
How it compares
MCP scraping integration via Smithery, not a local Playwright skill or a no-code scraper UI.
Common Questions / FAQ
Who is ai.smithery/ScrapeGraphAI-scrapegraph-mcp for?
It is for indie developers and agent users who want ScrapeGraphAI-style extraction callable from MCP clients during research and light data-gathering tasks.
When should I use ai.smithery/ScrapeGraphAI-scrapegraph-mcp?
Use it when you need fresh web content for idea validation, competitive research, or integration prototypes and prefer agent-driven tool calls over maintaining your own scraper repo.
How do I add ai.smithery/ScrapeGraphAI-scrapegraph-mcp to my agent?
Register the Smithery remote URL for @ScrapeGraphAI/scrapegraph-mcp in your MCP client and set Authorization to Bearer plus your smithery_api_key as required by the server headers.