---
title: Connect ChatGPT
description: Add looot as a connector in ChatGPT developer mode, sign in with the browser, and check it works.
sidebar:
  label: ChatGPT
---

<ClientHeader id="chatgpt" />

ChatGPT reaches looot through a connector, added in developer mode. Browser sign-in is the only
way; this connector form has no field for a header token.

Before you start you need a looot account. The runs you make spend the organization's balance, so
top up before your first paid run. See [Before your first run](/money#before-your-first-run).

:::note
Not tested by hand yet. Steps follow [the client's own docs](https://developers.openai.com/api/docs/guides/developer-mode); if a menu has moved, that page wins.
:::

## Sign in with the browser

The server URL is `https://api.looot.ai/mcp`. Nothing to copy: you sign in on looot.ai, pick the organization to bill and click **Connect**.

**Add the connector**

```text
1. Settings, Apps, Advanced settings: turn on Developer mode.
2. Click Create. Name: looot. MCP server URL: https://api.looot.ai/mcp. Authentication: OAuth.
3. Sign in on looot.ai, pick the organization, click Connect.
4. In a chat, open the + menu, Developer mode, and select looot.
```

## Headless: a token in the header

This client has no field for a header token. Browser sign-in is the only way.

## Notes

- Plus, Pro, Business, Enterprise and Edu, on the web.
- ChatGPT asks the user to confirm every call to a tool without readOnlyHint: true.

## Check it works

Ask ChatGPT to call [`balance`](/mcp-tools/balance) or [`catalog_overview`](/mcp-tools/catalog-overview). Both are free. A working connection answers
with your available balance, or the catalog's categories and job counts. ChatGPT asks you to
confirm any tool call that isn't marked read-only, so expect a confirmation prompt on a [`run`](/mcp-tools/run).

## What you see when you connect

The browser opens looot.ai and shows the consent page: which organization to bill, which scopes
to grant and how long to stay connected. See [The consent page](/connect#the-consent-page).

<Related />
