Connect an AI Agent

Connect Claude, Claude Code, Cursor, or any MCP client to your Ultimate Web Scraper cloud workspace — guided setup for Claude, access tokens for other agents.

Connecting an AI assistant to your cloud workspace takes about two minutes, and everything happens on one dashboard page. Claude gets a guided flow; every other MCP client connects with an access token the dashboard creates for you.

Where connections live

Open the cloud dashboard and go to Integrations. Two cards handle AI:

  • Claude — connects Claude (web and desktop) with a guided, sign-in based flow. Nothing to copy by hand, and the card shows the active connection so you can disconnect it anytime.
  • MCP — every other MCP-compatible agent: Claude Code, Cursor, and any client that supports remote MCP servers. This card is where you create, view, and revoke the workspace's access tokens.

Connect Claude

On the Claude card, click Connect Claude and follow the wizard — it walks you through adding Ultimate Web Scraper inside Claude's own settings, step by step. Once connected, ask Claude something like "what's in my latest extraction?" to confirm it can see your workspace. Disconnecting from the same card revokes Claude's access immediately.

Connect Claude Code, Cursor, or another MCP client

Create an access token

On the MCP card, click Create access token. Name it after the client it's for ("Claude Code — laptop", "Cursor") and pick an access level: read-only to analyze and query, or full access to also clean tables, operate automations, and start extractions.

Copy the ready-made setup

The moment the token is created, the dialog shows a paste-ready setup for your client — a terminal command for Claude Code, a configuration block for Cursor and other apps. Copy the one you need: the token is embedded in it, and it is shown only once.

Paste it into your client

Claude Code: paste the command into your terminal. Cursor: Settings → MCP → Add server. Other clients: add the block to your MCP configuration. Then ask the agent about your data — it discovers the workspace's tools automatically.

Lost a token?

Token values can't be viewed again after creation. If one gets lost, revoke it on the MCP card and create a fresh one — it takes seconds.

Managing your connections

The MCP card lists every active token with its name, access level, and when it was last used. Revoking a token cuts that client off instantly, and tokens stop working automatically if the person who created them leaves the workspace. Create one token per client, named after it, so revocation stays surgical.

Requirements

AI connections are part of paid plans — see /pricing. Once connected, reading, querying, cleaning, and exporting data consume no credits; agent-started extractions consume credits like any other cloud run, and always show an estimate before running.

On this page