Import.io Integrations

Import.io integrations.
Plug the web into everything you run.

Import.io integrations connect AI tools, developer frameworks, data platforms and business applications to live web data through MCP, the REST API, data endpoints, webhooks and managed delivery.

  • Integrations with setup guides50
  • Ways to connect6
  • MCP clients and frameworks with guides19
  • Hosted MCP endpoints1
  • Free MCP calls on signup10,000
MCPREST APIEndpointWebhookS3 / SFTPManaged Claude Code
terminal
# Install the Import.io Web Scraper pluginclaude plugin marketplace add import-io/mcp-pluginclaude plugin install import-io-web-scraper@import-io-plugins​# Or add the hosted server directlyclaude mcp add --transport http importio https://mcp.import.io/mcp \  --header "Authorization: Bearer $IMPORTIO_MCP_KEY"
Connects via Hosted MCP serverSetup 1 min
Full Claude Code guide

Find your tool.

Every entry has a setup example, the use cases teams run and a link to the docs. Filter by what you’re building or by how it connects.

Connects via

50 integrations

AI assistants & IDEs

The assistant your team already uses, with live web data as tools.

Agent frameworks & model APIs

Import.io tools inside the agents you build.

Spreadsheets & BI

Fresh web data in front of the people who decide.

Warehouses & databases

Web data next to the rest of your data.

AI training & retrieval

Extracted pages turned into indexes and datasets. Explore web data for AI training and retrieval.

Workflows & alerts

Work that starts the moment a run finishes.

Cloud storage & delivery

Files in your bucket, on your schedule.

Code & API

Extractors run and results pulled from your own code.

Six ways in.

Pick the path by who decides what gets fetched. A model deciding live: MCP. Your pipeline on a schedule: API, endpoints and webhooks. Nobody on your side at all: managed delivery.

Compare the six connection paths. On smaller screens, scroll the table sideways.

Six ways to connect Import.io: use cases, availability and authentication
Connection pathBest for / availabilityAuthenticationHow it works
Hosted MCP serverAI assistants, IDEs and agents that need to read live pages

Available: 10,000 free successful calls, then $0.0002 per call

OAuth, or Authorization: Bearer mcp_live_…

One endpoint, https://mcp.import.io/mcp, for every MCP client and agent framework. Interactive clients sign in with OAuth; scripts and servers send a bearer key.

Guides and documentation

Used by Claude, Claude Code, ChatGPT, Cursor, Windsurf, VS Code and 15 more.

MCP quickstart

REST API v2Pipelines that run extractions on their own schedule

Available: Every plan; full API on Professional and Advanced

_apikey query parameter

Start extractors, list runs and download results from api.import.io. Results come back as CSV, Excel or NDJSON.

Guides and documentation

Used by REST API, Python & pandas, Node.js, R, PostgreSQL, MySQL and 2 more.

REST API reference

Data endpointsSpreadsheets, BI tools and scripts that read the latest data

Available: Every plan; latest-run downloads don’t count as queries

The endpoint URL carries your key; keep it private

Stable URLs for the latest successful run as CSV or JSON, a Google Sheets formula, a run-history RSS feed and the Live Query API for a single URL.

Guides and documentation

Used by REST API, Python & pandas, Node.js, Google Sheets, Microsoft Excel, Power BI and 14 more.

Data endpoints

WebhooksWorkflows that should start the moment new data lands

Available: Every plan

Custom headers on the POST; send a shared secret

A POST to your URL each time a run succeeds, carrying the extractor ID, URL count and links to the run’s JSON, CSV and Excel files. Custom headers supported.

Guides and documentation

Used by Microsoft Excel, Zapier, Make, n8n, Power Automate, Slack and 3 more.

Using webhooks

File deliveryData teams that load from a landing zone

Available: Professional and Advanced

Credentials you issue for the bucket or server

Each run delivered as files into your Amazon S3 bucket or SFTP server, on the extractor’s schedule.

Guides and documentation

Used by Amazon Redshift, Databricks, Amazon S3, SFTP.

Plans and pricing

Managed deliveryEnterprise feeds you never want to maintain

Available: Managed Services and Aperture

Set up with your team at onboarding

A named team builds, runs and QAs the feed and delivers it into S3, Google Cloud Storage, Azure Blob, SFTP, Snowflake, BigQuery, API, email or Slack under an SLA. Aperture delivers into the same destinations.

Guides and documentation

Used by Power BI, Tableau, Looker Studio, Slack, Snowflake, BigQuery and 8 more.

Managed Services

Stacks teams run.

Integrations earn their keep in combination. Four we set up again and again.

Competitor prices in Snowflake before the 9am meeting

A scheduled feed lands in Snowflake overnight, QA’d, and the Tableau dashboard opens on yesterday’s market.

  1. Extractor schedule
  2. Managed delivery
  3. Snowflake
  4. Tableau

An agent that answers from the live web

Your product calls Claude with the Import.io MCP attached. Claude fetches the page, extracts the fields and answers with the source.

  1. Your app
  2. Claude API
  3. Import.io MCP
  4. importio_extract_data

A price sheet that updates itself

One IMPORTDATA formula in a Google Sheet, a daily extractor, and a Looker Studio report the whole team can open.

  1. Daily extractor
  2. Google Sheets
  3. Looker Studio

MAP violations where brand teams already work

Aperture detects MAP risk and posts it to Slack and email with retailer, price and evidence.

  1. Aperture
  2. Slack
  3. Email

Or connect nothing.

Managed Services and Aperture deliver into the destination you already run. A named team builds, runs and QAs the feed under an SLA with fees at risk.

Your schema

Fields, types and format agreed up front and held run after run.

QA before delivery

Every delivery is checked before it reaches your destination.

Protected sources handled

Heavily defended sites and logins are the team’s problem, not yours.

One contract

Dedicated capacity, custom volumes and terms to suit.

Integration questions.

What can I connect Import.io to?

50 documented integrations across six connection paths: AI assistants, IDEs and agent frameworks through the hosted MCP server; code, spreadsheets and BI through the REST API and data endpoints; workflow tools through webhooks; and storage, warehouses and alerting through S3 and SFTP delivery or Managed Services.

What is the difference between the MCP server and the REST API?

The MCP server gives an AI model tools: it decides what to fetch and calls Import.io live. The REST API runs extractors you have built, on your schedule, and returns their results. Agents use MCP; pipelines use the API, endpoints and webhooks.

Which MCP clients work with Import.io?

Any client that connects to remote MCP servers over HTTP. Claude, Claude Code, ChatGPT, Cursor, Windsurf, VS Code, Cline and Gemini CLI have step-by-step guides here, as do the Claude and OpenAI APIs, the OpenAI Agents SDK, LangChain, LlamaIndex, CrewAI, the Vercel AI SDK, Google ADK, Copilot Studio and n8n.

Do downloads count against my plan?

No. The latest-run CSV, JSON and Google Sheets endpoints return data your extractor already collected. Queries are counted when pages are extracted, not when you read the results.

Can Import.io deliver straight into our warehouse?

Yes. Managed Services and Aperture deliver into Snowflake, BigQuery, Amazon S3, Google Cloud Storage, Azure Blob Storage, SFTP, API, email and Slack. On self-service plans, Professional and Advanced deliver into S3 and SFTP, and the guides here load Postgres, MySQL, SQL Server, MongoDB, BigQuery and Snowflake in a few lines.

How do webhooks work?

Add a URL and optional headers in the extractor’s settings. Every successful run sends a POST with the extractor ID, total URL count and links to the run’s JSON, CSV and Excel files. Webhook delivery is on every plan.

Is there a Zapier or Make app?

You don’t need one. Both connect through their webhook triggers, and Zapier can also watch the run-history RSS feed. Every action in those tools works after the trigger.

What does it cost?

The MCP server includes 10,000 free successful calls, then $0.0002 per successful call, with a monthly spend limit. Extraction plans start with a free 30-day trial and run from $199 a month, billed on successful queries only. Managed Services and Aperture are priced by contract.

Your stack already
speaks Import.io.