Skip to main content
The lobstr.io MCP Server lets an AI client operate your lobstr.io account directly. Discover a scraper, read its inputs, run it, watch the run, and pull results — without leaving the chat and without manual CSV export/import. Endpoint: https://mcp.lobstr.io/mcp

15 Tools

Discover scrapers, run and monitor them, fetch results, and check your credits and connected platform accounts.

OAuth

Connect with your own lobstr.io login. You approve on lobstr.io — no password ever reaches the AI client.

Streamable HTTP

Standard MCP transport, compatible with Claude, ChatGPT, Cursor, and Codex.
This is the operational server — it acts in your account and spends credits. For a public, no-auth assistant that only answers questions about the API docs, see the Documentation MCP.

​
Before you start

  • A lobstr.io account with credits — running a scraper spends credits from your balance.
  • An MCP-capable client (Claude, ChatGPT, Cursor, Codex, …).
No client ID or secret to paste: the server supports Dynamic Client Registration, so your client registers itself.

​
Setup

Claude.ai and ChatGPT — add it as a custom connector in settings, using https://mcp.lobstr.io/mcp. Both drive the sign-in flow for you. Codex CLI — register it as a remote MCP server in ~/.codex/config.toml using the same URL (key names vary by version; check the Codex docs). After adding the server, your client opens the lobstr.io consent page: you’re already signed in, you click Allow, and you’re returned to the client. On a headless box the authorize URL is printed for you to open in a browser.

​
Connecting your account

The server uses OAuth 2.1 with PKCE. You approve the connection on lobstr.io’s own site, so no password is ever sent to the AI client or to the MCP server. You choose what to allow, per these scopes: You can revoke access at any time from your lobstr.io account.

​
Tools

A crawler is a scraper template (e.g. “Google Maps”); a squid is one you’ve configured from it. A run is one execution of a squid.

​
Discover & inspect

​
Run & monitor

​
Results

​
Your account

​
Connected accounts

The platform logins your scrapers authenticate with (LinkedIn, Facebook, …) — distinct from your lobstr.io account above. These return metadata only — never credentials or cookies. New scrapers work automatically — get_scraper_details reads each scraper’s live input schema, so nothing here needs updating when lobstr.io adds one.

​
Credits and confirmation

Running a scraper spends credits, and lobstr.io prices per result row — so the total isn’t known until the run completes. run_scraper estimates the cost and, when it’s above a threshold or unknown, returns a confirmation request instead of running; the client asks you, and only then does it execute. The read tools never spend credits.

​
A typical conversation

  1. “Find a scraper for Google Maps business leads.” → search_scrapers
  2. “What inputs does it need?” → get_scraper_details
  3. “Run it for dentists in Manchester.” → run_scraper (asks you to confirm)
  4. “Is it done?” → get_run
  5. “Show me the results.” → get_results

​
Troubleshooting

The client can’t authorize / the connection fails. The server must be reached over HTTPS at https://mcp.lobstr.io/mcp. Make sure you copied the full URL including /mcp. Every run asks for confirmation. Expected — lobstr.io prices per row, so the total is unknowable up front. The estimate still shows the per-row rate. A run stays pending or errors. Check the run in your lobstr.io dashboard; the MCP surfaces the same status your account shows.