Skip to main content
Claude can operate your lobstr.io account directly through the lobstr.io MCP server. Instead of switching to the dashboard to pick a scraper, add tasks, launch, wait, and download a CSV, you describe what you want in plain language and Claude does it in your account. Endpoint: https://mcp.lobstr.io/mcp
This is the operational server — it acts in your account and spends credits. There is also a separate, public documentation server at https://docs.lobstr.io/mcp that only answers questions about the lobstr.io API and can’t touch your account.

​
Before you start

  • A lobstr.io account with credits — launching a run spends credits from your balance.
  • Claude on the web, Claude Desktop, or Claude Code.
You don’t need your API key for this. The connection uses OAuth: you approve it on lobstr.io’s own site, so no password ever reaches Claude.

​
Watch the setup walkthrough

​
Connect Claude to lobstr.io

1

Open your connector settings

In Claude, go to Settings → Connectors, then click Add custom connector.
2

Paste the lobstr.io endpoint

Give the connector a name (for example, lobstr.io) and paste the full URL:
Include the trailing /mcp. A URL without it won’t connect.
3

Approve the connection

Claude opens the lobstr.io consent page. You’re already signed in, so you just review the permissions and click Allow. Claude returns to the conversation with the connector enabled.

​
What you’re approving

The consent page lists the permissions Claude is asking for, and you choose which ones to allow. You can revoke access at any time from your lobstr.io account.

​
What Claude can do

New scrapers work automatically. Claude reads each scraper’s live input schema, so nothing needs updating when lobstr.io adds one to the store.

​
Scrapers that need a synced account

Some scrapers log in to a platform on your behalf, such as the LinkedIn and Sales Navigator scrapers. They need a synced account first, set up with Account sync.
  • One matching account: if exactly one healthy synced account of the right type exists, Claude attaches it for you.
  • Several or none: Claude asks you which account to use, or tells you which platform to sync.
  • The type must match. A LinkedIn account can’t run a Sales Navigator scraper, and the reverse.
  • Attaching only adds. An account already on a Squid is never swapped out.

​
A typical conversation

Here’s a full run from start to finish — finding a scraper, launching it, and reading the results back in the chat.
1

Find a scraper

“Find me a scraper for Google Maps business leads.”
2

Check what it needs

“What inputs does it take, and what does it cost?”
3

Launch the run

“Run it for dentists in Manchester.” — Claude asks you to confirm the cost before it launches.
4

Follow the run

“Is it finished?”
5

Get the data

“Show me the results.”

​
Credits and confirmation

lobstr.io prices per result row, so the final cost of a run isn’t known until it finishes. Before launching, Claude estimates the cost — and when the estimate is high or can’t be calculated, it asks you to confirm instead of launching straight away. Reading scrapers, runs, and results never spends credits. For a closer figure before anything launches, ask Claude to estimate the run once the Squid has its tasks. If email verification is on, it’s billed separately after the scrape.
Runs launched from Claude are real runs in your account. They appear in your dashboard with an mcp badge next to the Squid name, count against your slots, and draw down the same credit balance as runs you launch yourself.

​
Troubleshooting

Check the URL is exactly https://mcp.lobstr.io/mcp, over HTTPS and with the /mcp path included.
That’s expected. lobstr.io charges per row, so the total is unknowable up front — the estimate shows you the per-row rate so you can decide.
Open the run in your lobstr.io dashboard. Claude sees the same status your account does, so the dashboard will show the same stop reason.
Confirm you clicked Allow on the consent page and that your balance isn’t empty. You can re-approve the connector from your Claude settings.
Your plan caps the total slots your active Squids can reserve. The cap is checked when a Squid is created, activated, or has its slots raised, not when a run starts. If creating a Squid fails because you’re at the limit, deactivate Squids you don’t need from the dashboard, or ask Claude to do it. After a plan change the count can read above your limit; Squids that already exist keep running.
On the free plan, reading results through the MCP server is capped at the first 30 rows. Upgrading your plan is the only way past it. See Manage subscription.