AI Agents & MCP Overview

Connect Claude and other AI assistants to your Ultimate Web Scraper cloud workspace via MCP. Analyze, clean, and launch extractions in plain language.

Early access

AI connections are rolling out now. The MCP server is live for cloud workspaces, with broader public availability on the way.

Ultimate Web Scraper speaks MCP (Model Context Protocol) — the open standard that lets AI assistants like Claude, Claude Code, and other MCP-compatible clients connect to your tools. Once connected, your AI assistant can work with your scraped data conversationally:

"Which of the 2,000 companies I scraped yesterday don't have an email address?"
"Clean up this table — drop the junk columns and merge street, city, and zip into one address."
"Run my price-monitoring automation again and tell me when it's done."
"Take the product links from that table and extract full product data for each."

How it works

You connect from the cloud dashboard's Integrations page: Claude gets a guided connect flow, and every other MCP client — Claude Code, Cursor, and friends — uses a personal access token created there, with a paste-ready setup for each client. From then on, the agent can list your result tables, query them, clean them, check on runs, start new extractions, and answer questions about how the product works straight from these docs — all through natural conversation, and all scoped to your workspace.

🚀

Claude overview

What connecting Claude to Ultimate Web Scraper looks like, in three steps.

🌐

MCP overview

Web scraping over MCP — every AI app it works with, and how to connect each one.

🔌

Connect an AI agent

Two minutes from the Integrations page to a working connection — Claude, Claude Code, Cursor, and more.

✨

What agents can do

Query tables of any size, clean columns and rows, export, operate automations, and get product help.

🧰

MCP tool reference

Every tool a connected agent can use, grouped by access level.

🪄

AI-started extractions

Ask your assistant to extract product data, emails, social links, phones, or Google Maps places.

🛡️

Security model

Workspace-scoped tokens, read-only mode, revocation, and credit safety.

Cloud-only, by design

AI agents connect to your cloud workspace only. Data extracted locally with the Chrome extension stays on your machine — it is never exposed to agents unless you run the extraction in the cloud. This is the same privacy boundary as the rest of the product: local means local.

Selector-based scrapers (like List Extractor configurations) are still authored visually in the extension. Agents can run them in the cloud and use their results — building them stays point-and-click.

Which AI apps work?

Any MCP-compatible client, including:

Claude (web and desktop) via custom connectors
Claude Code in the terminal
Cursor and other MCP-capable editors and agents

Setup for each lives in Connect an AI agent.

Requirements

A cloud workspace on a paid plan (token creation is part of paid plans — see Credits & plans)
Reading, querying, cleaning, and exporting data consume no credits; agent-started extractions consume credits like any other cloud run