> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobstr.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect lobstr.io to ChatGPT and run scrapers from a conversation

> Add the lobstr.io MCP server to ChatGPT as a custom connector so you can find a scraper, launch a run, and pull the results without leaving the chat.

ChatGPT can operate your lobstr.io account directly through the lobstr.io **MCP server**. You describe what you need in plain language, and ChatGPT finds the right scraper, launches the run in your account, and reads the results back to you.

**Endpoint:** `https://mcp.lobstr.io/mcp`

<Note>
  This is the **operational** server — it acts in your account and spends credits. A separate public server at `https://docs.lobstr.io/mcp` only answers questions about the lobstr.io API and can't touch your account.
</Note>

## Before you start

* A [lobstr.io account](https://app.lobstr.io) with credits — launching a run spends credits from your balance.
* ChatGPT on the **web**, on a plan where custom connectors are available (Plus, Pro, Business, Enterprise, or Edu).

You don't need your API key. The connection uses OAuth: you approve it on lobstr.io's own site, so **no password ever reaches ChatGPT**.

<Note>
  On Business and Enterprise workspaces, an admin may need to allow custom connectors before the option appears for you.
</Note>

## Watch the setup walkthrough

<iframe width="100%" height="420" src="https://www.loom.com/embed/7ac26e3bd1dc4cde91c9577cfa5b4e4b" frameborder="0" allowfullscreen />

## Connect ChatGPT to lobstr.io

<Steps>
  <Step title="Turn on developer mode">
    In ChatGPT on the web, go to **Settings** → **Apps** → **Advanced settings** and switch on **Developer mode**.

    The button for creating custom connectors only appears once this is on.
  </Step>

  <Step title="Create the connector">
    Go to **Settings** → **Connectors** and create a new custom connector. Name it `lobstr.io` and paste the full URL:

    ```
    https://mcp.lobstr.io/mcp
    ```

    <Warning>
      Include the trailing `/mcp`. A URL without it won't connect.
    </Warning>
  </Step>

  <Step title="Choose OAuth and approve">
    lobstr.io authenticates with OAuth, so pick that option if ChatGPT asks. It opens the lobstr.io consent page — you're already signed in, so review the permissions and click **Allow**.
  </Step>

  <Step title="Enable it in a chat">
    Back in ChatGPT, turn the lobstr.io connector on for the conversation you want to use it in.
  </Step>
</Steps>

## What you're approving

The consent page lists the permissions ChatGPT is asking for. You can revoke access at any time from your lobstr.io account.

| Permission      | What it grants                              |
| --------------- | ------------------------------------------- |
| `crawlers:read` | Discover scrapers and read their settings   |
| `runs:read`     | Check the status of your runs               |
| `results:read`  | Read your scraped results                   |
| `account:read`  | View your account and credit balance        |
| `runs:execute`  | Launch runs on your behalf (spends credits) |

## What ChatGPT can do

| Capability                                             | Spends credits |
| ------------------------------------------------------ | -------------- |
| Search the 40+ scrapers in the store for the right one | No             |
| Read a scraper's inputs, output fields, and pricing    | No             |
| List and inspect your saved Squids                     | No             |
| Launch a run                                           | **Yes**        |
| Check a run's status and progress                      | No             |
| Read a page of results from a run                      | No             |

## A typical conversation

Here's a complete run in ChatGPT — finding a scraper, launching it, and pulling the results back into the chat.

<iframe width="100%" height="420" src="https://www.loom.com/embed/c05e8cf1cdbb4b70a85eda4db9ba5086" frameborder="0" allowfullscreen />

<Steps>
  <Step title="Find a scraper">
    *"Find me a scraper for TripAdvisor restaurant reviews."*
  </Step>

  <Step title="Check what it needs">
    *"What inputs does it take, and what does it cost per row?"*
  </Step>

  <Step title="Launch the run">
    *"Run it on these three restaurant pages."* — ChatGPT asks you to confirm the cost before it launches.
  </Step>

  <Step title="Follow the run">
    *"Is it finished?"*
  </Step>

  <Step title="Get the data">
    *"Show me the results as a table."*
  </Step>
</Steps>

## Credits and confirmation

lobstr.io prices **per result row**, so the final cost of a run isn't known until it finishes. Before launching, ChatGPT estimates the cost — and when the estimate is high or can't be calculated, it asks you to confirm first. Reading scrapers, runs, and results never spends credits.

<Warning>
  Runs launched from ChatGPT are real runs in your account. They appear in your dashboard, count against your slots, and draw down the same credit balance as runs you launch yourself.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="I can't find the option to add a custom connector">
    Developer mode isn't on, or your plan or workspace doesn't allow custom connectors. Check **Settings** → **Apps** → **Advanced settings** first, and ask your workspace admin if you're on Business or Enterprise.
  </Accordion>

  <Accordion title="The connection fails or ChatGPT can't authorize">
    Check the URL is exactly `https://mcp.lobstr.io/mcp`, over HTTPS and with the `/mcp` path included.
  </Accordion>

  <Accordion title="Every run asks me to confirm">
    That's expected. lobstr.io charges per row, so the total is unknowable up front — the estimate still shows you the per-row rate.
  </Accordion>

  <Accordion title="A run stays pending or errors out">
    Open the run in your [lobstr.io dashboard](https://app.lobstr.io). ChatGPT sees the same status your account does, so the dashboard will show the same [stop reason](/core-concepts/run-stop-reasons).
  </Accordion>
</AccordionGroup>