← All integrations
Import.io + Build on Import.io

Build Import.io into your AI product

If your product is an MCP client, your users can connect their own Import.io Web Scraper MCP account with OAuth and get hosted scraping, proxies and extraction as tools.

Connects via
MCP
Setup
1 day
Available on
10,000 free successful calls, then $0.0002 per call
Category
Code & API
Talk to salesSee Managed Services
Endpoint
MCP endpoint   https://mcp.import.io/mcp
Auth           OAuth, started when the server requests it
Fallback       Authorization: Bearer mcp_live_…
Billing        Per successful call, on the user’s account

How it connects.

Source

The web

Any public page, rendered, through managed proxies

Engine

Import.io

Rendering, proxy routing, captcha handling, extraction

Path

Import.io MCP

https://mcp.import.io/mcp

Destination

Build on Import.io

Offer Import.io web data tools inside your own agent platform with OAuth.

What teams do with it.

Web data tools for your users

Add a “Connect Import.io” button and your agent platform can read the defended web.

Each user on their own account

OAuth scopes usage to the user’s Import.io account, their free calls and their spend limit.

Nothing to host

The scraping engine, browsers and proxies stay on Import.io. You implement the OAuth flow and call tools.

Set it up.

  1. Call https://mcp.import.io/mcp. When the server asks for authentication, start the OAuth authorization flow.
  2. Retry the MCP request with the granted credentials.
  3. Store tokens in your credential store, not in project files, and refresh them before they expire.
  4. Surface authentication errors clearly so users can reconnect.

Questions.

Can we resell Import.io inside our product?

Talk to us. Partnerships for platforms that bundle web data are handled by the sales team.

What does the Import.io MCP cost?

Signup includes 10,000 successful calls. After that it is $0.0002 per successful call. Setup requests, tool listings, malformed requests, blocked requests and failed upstream calls are never billed, and you can set a monthly spend limit that stops paid usage when reached.

OAuth or API key?

Use OAuth in interactive clients that support it: the client opens a sign-in, stores the credentials and reuses them. Use an API key for scripts, servers and clients without OAuth, sent as Authorization: Bearer mcp_live_…. Keep keys out of prompts and shared config files.

Which tools does the server expose?

importio_web_fetch, importio_render, importio_extract_data and importio_get_html, page helpers such as importio_page_text, importio_page_links and importio_search_cards, and browser actions for clicks, form input, scrolling, pagination, waits, screenshots and captcha handling. Requests can pick a proxy country and type, with bounded retries when a page blocks.

Related integrations.

All 50 integrations

MCP

MCP SDKs

Call Import.io tools directly from the official Python and TypeScript SDKs.

Setup 10 minMCP

Claude API

Pass one server in mcp_servers and Claude calls Import.io tools server-side.

Setup 5 minMCP

OpenAI API

Add Import.io as a remote MCP tool in the Responses API.

Setup 5 minMCP

Claude

Live, structured web data as tools in Claude on the web and Claude Desktop.

Setup 2 min

Build on
the live web.

Talk to salesSee Managed Services