Works with your whole agent stack
One hosted MCP server connects Claude, Cursor, Codex, and any MCP-aware tool in a single line, plus native SDK adapters where it counts. We label how each one connects: a first-party package, the hosted MCP, or a third-party hub. No overclaiming.
Planned first-party SDK package. Not published yet, call the REST API today.
Connects through the hosted MCP server. No adapter, one URL of config.
Reaches SuperScraper through a third-party catalog or hub.
Native SDK adapters
A first-party LangChain document loader and tools. Drop SuperScraper into a chain or agent and get clean, LLM-ready content back.
A LlamaIndex (TypeScript) reader that turns any URL into nodes ready for indexing and retrieval.
A first-party CrewAI tool (Python) so your crew can scrape, crawl, and extract the live web mid-task.
Tools for the Vercel AI SDK (TypeScript). Give a model live web access inside generateText / streamText tool calls.
A first-party tool for the Google Agent Development Kit (Python). Wire SuperScraper into an ADK agent.
MCP hosts
Claude Code and Claude Desktop connect via the hosted MCP server. No adapter, one URL of config gives Claude live web access.
Add SuperScraper to Cursor as a remote MCP server and the editor agent can scrape, crawl, and extract the web in-context.
The OpenAI Codex CLI speaks MCP. Point it at the hosted server to give it live web fetch and extract.
Cline (the VS Code agent) connects via MCP. Add the hosted server and Cline gains clean, LLM-ready web access.
Windsurf and Devin Desktop are MCP-aware. Register the hosted server and the agent can pull the live web.
NousResearch's Hermes connects through MCP. Point it at the hosted server for live web fetch and extraction.
Mastra agents consume MCP servers. Add SuperScraper as a remote MCP server and its tools appear in your workflow.
Add SuperScraper to ChatGPT as a custom connector, or build a Custom GPT Action from the OpenAPI spec. Either way ChatGPT can fetch and extract the live web.
All product names, logos, and brands are property of their respective owners. Listing a tool indicates compatibility, not endorsement or affiliation. Logos are sourced from simple-icons (CC0); where a logo isn't available, a text monogram is shown.
Don't see your tool?
If it speaks MCP, it already works. Point it at the hosted server. Otherwise the REST API and SDKs drop into any loop.