← All integrations

Web Scraper Cloud MCP server

4 operations0 webhooks

Web scraping with Web Scraper Cloud - list and read sitemaps with their selectors and start URLs, create a sitemap from an exported definition, and read the account's page credits.

Try Web Scraper Cloud with your agent

Connect Web Scraper Cloud, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Web Scraper Cloud on my account, then run one read-only example and show me the result.

Runs once, when you ask

Web Scraper Cloud tools and triggers

Tools are what your agent can do in Web Scraper Cloud through Corsair's MCP server. Triggers are the Web Scraper Cloud events a routine can start from.

Sitemaps

  • CreateWrite

    Create a sitemap from the definition the browser extension exports, selectors included

    sitemaps.create

  • GetRead-only

    Read one sitemap: its id, name and definition (start URLs and selectors) as a JSON string

    sitemaps.get

  • ListRead-only

    List the sitemaps on the account (id and name), a page at a time, optionally filtered by tag

    sitemaps.list

Account

  • GetRead-only

    Read the account user and the page credits left; the cheapest way to check a token

    account.get

Connect Web Scraper Cloud to Claude, ChatGPT or Cursor

  1. 1

    Connect Web Scraper Cloud in Corsair

    Add your Web Scraper Cloud API key once in Corsair. Corsair stores the credential encrypted and makes the Web Scraper Cloud API calls for your agent, so it never goes into a prompt or a config file. Connect Web Scraper Cloud

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Web Scraper Cloud. On a ChatGPT personal plan, connect Web Scraper Cloud here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. None of Web Scraper Cloud's operations are destructive, so in the default Cautious mode they all run right away. Strict mode asks before each of its 1 write, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/webscraperio, add the Web Scraper Cloud plugin, and connect with an API key. Then call methods like corsair.webscraperio.api.account.get() from your app. Corsair keeps each tenant isolated.

Yes. Web Scraper Cloud requires an API key from your Web Scraper Cloud account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Web Scraper Cloud, GitHub, Notion, Stripe, and the rest. Trigger Web Scraper Cloud from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for web scraping with Web Scraper Cloud - list and read sitemaps with their selectors and start URLs, create a sitemap from an exported definition, and read the account's page credits. Common builds include sync jobs, admin tooling, and agents that call Web Scraper Cloud APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Web Scraper Cloud API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/webscraperio in the open repo. When Web Scraper Cloud ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Web Scraper Cloud data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Web Scraper Cloud data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Web Scraper Cloud on a link in Strict mode and every write waits for your approval, while destructive actions are refused. None of the Web Scraper Cloud operations are destructive, so the default Cautious mode runs them all without asking. You can change a link's mode at hub.corsair.dev/me.