Skip to content

docs: update MCP docs for scrapegraph-mcp v3 rename#68

Merged
VinciGit00 merged 1 commit intomainfrom
docs/mcp-v3-rename
Apr 30, 2026
Merged

docs: update MCP docs for scrapegraph-mcp v3 rename#68
VinciGit00 merged 1 commit intomainfrom
docs/mcp-v3-rename

Conversation

@Vikrant-Khedkar
Copy link
Copy Markdown
Collaborator

Summary

scrapegraph-mcp v3.0.0 renamed 7 MCP tools to match the v2 API canonical names. This PR brings docs.scrapegraphai.com in sync.

Renames documented

v2 (old) v3 (new)
smartscraper extract
searchscraper search
smartcrawler_initiate crawl_start
smartcrawler_fetch_results crawl_get_status
sgai_history history
generate_schema schema
markdownify removed — use scrape with output_format="markdown"

What changed

  • services/mcp-server/introduction.mdx — tool table updated to v3 (17 tools, was 18). Migration callout added linking to the v3.0.0 release notes.
  • services/schema.mdx (new) — canonical page for the schema tool / POST /schema endpoint. Was missing entirely.
  • docs.json — added services/schema to the v2 Services nav.
  • services/mcp-server.mdx — was a 363-line stale duplicate that referenced a 404 openapi.json. Replaced with a slim redirect to mcp-server/introduction plus client setup cards. Inbound links from google-adk.mdx, smithery.mdx, and introduction.mdx still resolve.
  • Deprecation banners on legacy v1 service pages, each pointing at the v2/v3 canonical replacement:
    • services/markdownify.mdxservices/scrape
    • services/smartscraper.mdxservices/extract
    • services/searchscraper.mdxservices/search
    • services/smartcrawler.mdxservices/crawl
    • services/agenticscraper.mdx → marked removed in v2
    • services/sitemap.mdx → marked removed in v2

Out of scope (intentional)

  • SDK method-name references (integrations/x402.mdx, integrations/agno.mdx, services/additional-parameters/{pagination,wait-ms,headers}.mdx) — those track the Python SDK API, not MCP tool names. Separate rename track if/when scrapegraph-py renames its methods.
  • v1 doc tree under docs.json legacy nav — frozen historical reference.

Test plan

  • mint broken-links — no NEW broken links introduced (pre-existing v1-endpoint broken refs in legacy pages remain; users now hit deprecation banners first)
  • grep sweep across services/mcp-server/ and docs.json returns zero unintended old-name hits (only the migration callout + v1 legacy nav block, both intentional)
  • All deprecation-banner targets (services/scrape, services/extract, services/search, services/crawl) resolve to existing v3 canonical pages
  • Local Mintlify preview: mint dev → load /services/mcp-server/introduction → confirm 17-tool table, all internal links resolve

After merge

🤖 Generated with Claude Code

scrapegraph-mcp v3.0.0 renamed 7 MCP tools to match the v2 API canonical
names. This brings the docs in sync.

Changes:
- services/mcp-server/introduction.mdx: replace tool table with v3 names
  (smartscraper→extract, searchscraper→search, smartcrawler_initiate→
  crawl_start, smartcrawler_fetch_results→crawl_get_status, sgai_history→
  history, generate_schema→schema, markdownify removed). Tool count
  18→17. Added v2→v3 migration callout.
- services/schema.mdx: NEW canonical page for the schema tool /
  POST /schema endpoint (was missing).
- docs.json: add services/schema to v2 Services nav.
- services/mcp-server.mdx: replaced 363-line stale duplicate (referenced
  a 404 openapi.json) with a slim redirect to introduction.mdx + setup
  guide cards.
- Deprecation banners on legacy v1 service pages pointing to v2/v3
  canonical pages: markdownify→scrape, smartscraper→extract,
  searchscraper→search, smartcrawler→crawl. agenticscraper and sitemap
  marked as removed in API v2.

Out of scope: SDK method-name references (x402, agno, additional-parameters
examples) — those track the Python SDK separately.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@VinciGit00 VinciGit00 merged commit 2293f1b into main Apr 30, 2026
2 checks passed
@VinciGit00 VinciGit00 deleted the docs/mcp-v3-rename branch April 30, 2026 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants