Dynamic pages need a browser.
Run JavaScript, wait for the interface and interact with controls before extracting.
Hosted MCP · available now
Web scraping.Built for AI.
Bring browser rendering, proxy routing, CAPTCHA handling and structured extraction into Claude, ChatGPT, Cursor, Codex and any compatible MCP client. You connect; Import.io runs the scraping infrastructure.
10,000 successful calls free · no credit card required
YOU
Scrape the top five stories from Hacker News and return title, points and link.
- 01importio_renderRender the live page
- 02importio_extract_dataApply the requested schema
- 03structured resultReturn only useful fields
Select “Play sequence” to see how the tools cooperate. No network request is made.https://mcp.import.io/mcp
10,000free successful calls
$0.0002per successful call after
OAuthor bearer API key
Hostedno scraping stack to run
Connect in minutes
One endpoint. Your client.
Choose the client you already use. The configuration below is real, copyable and paired with the right authentication path.
01 · Choose your clientSelect a logo to update the setup
02CLAUDE SETUP
AUTH EXAMPLE
Install the Import.io plugin in Claude, then use hosted web scraping tools directly in the conversation.
Why a scraping MCP
Browsing finds a page. This returns usable data.
Repeatable extraction needs a browser, geographic control and a schema, not a wall of HTML in the model context.
Location changes the answer.
Target the country your workflow needs so price, stock and content reflect the right market.
Raw pages waste context.
Return the requested fields as structured data instead of sending full HTML to the model.
Blocks should not stop the agent.
Proxy routing and CAPTCHA handling sit behind the tool call, not inside your workflow.
Tool explorer
Give the agent the right web primitive.
Explore what each tool contributes to the workflow. The example input and result change with the selected tool.
Render the page the way a user sees it.
Use a hosted browser for JavaScript, lazy loading and interactive content before another tool extracts or inspects the result.
INPUT
RETURNS
Use it when the page depends on JavaScript or browser state.
How it fits together
Your agent asks. Import.io does the web work.
One hosted endpoint sits between the client and a production scraping engine. The result returns in the form the workflow requested.
CLIENTClaude · ChatGPT
Cursor · Codex
→Cursor · Codex
HOSTED MCPRender · act
extract · inspect
→extract · inspect
RESULTJSON · HTML
screenshots
screenshots
Simple usage pricing
Pay for results. Not attempts.
Start with 10,000 successful tool calls free. After that, pay $0.0002 per successful call and set a monthly spending limit you control.
$0.0002per successful tool call
- Successful render or actionBilled
- Successful screenshot or extractionBilled
- Malformed or failed upstream requestNot billed
- Blocked requestNot billed
Proxy routing, country targeting and CAPTCHA support included.
Questions developers ask.
The short version. The complete setup and tool reference lives in the MCP documentation.
How is this different from built-in browsing?+
Built-in browsing is useful for one-off access. Import.io adds hosted browser execution, proxy routing, country targeting, CAPTCHA handling and structured extraction for repeatable workflows.
How do I connect it?+
Add https://mcp.import.io/mcp to your compatible client. Most clients start OAuth automatically; scripts and clients without OAuth can use a bearer API key.
What counts as a billable call?+
Only successful tool calls. Malformed requests, blocked requests and failed upstream calls are not billed.
Can I control spend?+
Yes. Set a monthly spending limit in billing. Paid usage stops when the configured limit is reached.
INTEGRATIONS
Works with your MCP client.
Connect the hosted server from your assistant, coding environment or agent framework.
See all integrationsHosted MCP · available now
Give your agenta real web-scraping engine.
Connect any compatible MCP client and start with 10,000 free successful calls.