# Connect ChatGPT to Laabam.site

Ten minutes, once. After this, ChatGPT can answer questions about your websites and build new ones for you without spending Laabam.site credits.

You need a ChatGPT account that can add connectors — that is **Plus, Pro, Business or Enterprise**. The free tier cannot.

## The address you will need

```
https://api.laabam.site/api/mcp
```

Copy that exactly. Keep this page open — you will paste it in step 3.

## Step by step

1. In ChatGPT, open **Settings → Connectors** (on some plans it is under **Apps**).
2. Turn on **Developer mode** if you see it. Custom connectors live behind it.
3. Choose **Add custom connector** or **Create**, and paste the address above.
4. Give it a name — "Laabam.site" is fine — and save.
5. ChatGPT sends you to Laabam.site to sign in. Sign in with the account that owns your websites.
6. You land on a permission screen. Read it, tick what you want, press **Allow**.

## The permission screen

You will see what the assistant can read, what it can never see, and **two unticked boxes**:

- **Also let it propose new websites** — tick this if you want ChatGPT to be able to build sites for you. Without it, ChatGPT can only answer questions.
- **Also let it read your website's code** — tick this so it can match your existing design. Needs a paid plan; on a free account the tools stay locked even if you tick it.

Both are off by default on purpose. Being asked for a permission is not the same as granting it.

If you only see **one** box, ChatGPT did not ask for code access. Remove the connector and add it again — see _It is showing me the wrong thing_ below.

## Check it worked

Start a **new chat** and ask:

```
List every tool you have available from the Laabam.site connector,
with their exact tool names. Don't call any of them yet.
```

You should get **ten** tools, ending in `list_sites`, `upload_website`, `list_site_files` and `get_site_file`. If you tick only the proposal box and not code access, you will see eight — that is correct, the two code tools are hidden.

If you see a tool called `create_website`, you are looking at a cached list. See below.

## Build something

```
Use my Laabam.site connector.

Call list_sites first.

Then YOU design and write a complete one-page website for a
Chettinad restaurant in Madurai called "Meenakshi Mess" — hero, a
menu of about 8 dishes with rupee prices, timings, location, and a
contact form. Write all the HTML and CSS yourself. Do not ask Laabam.site
to build it.

Call upload_website with the finished files, including an index.html,
and give me the reviewUrl it returns.

Report it as awaiting my approval. Do not say it is live.
```

ChatGPT will write the site and send it. It should come back saying the proposal is **awaiting your approval**, with a link. It has not published anything.

Open **Settings → AI connections** in your Laabam.site dashboard, press **Review code** to read what it wrote, then **Publish it**.

## Matching your existing design

Once you have a site and have granted code access:

```
Use my Laabam.site connector. Call list_sites, then list_site_files on
my site and get_site_file on its index.html.

Now write a second page — "Catering" — that matches that site's
existing design exactly: same fonts, colours, header and footer
markup. Upload it with upload_website.
```

Reading the real files is what makes the result match. Without it the assistant is guessing at your design from a description, and it shows.

---

## When something goes wrong

### It is showing me the wrong thing

**Symptom:** the tool list is missing something, or has a tool that no longer exists, or the permission screen only offers one checkbox.

ChatGPT caches a connector against its **exact URL**, and that cache survives removing and re-adding the app. Re-authorising your account does not clear it either.

**The fix:** add the connector again with a URL that differs by one character:

```
https://api.laabam.site/api/mcp/
```

The trailing slash. It is the same endpoint on our side, but a different string to ChatGPT, so there is nothing cached for it and it registers fresh. Then start a **new chat** — an existing conversation keeps the tool list it started with.

### It asks me to approve every single thing

Reading your account should not prompt. If ChatGPT is confirming every question, make sure your connector permission is at least **Allow low-risk actions** in its settings — that is the default, and Laabam.site marks all its read tools as read-only so they pass without asking.

ChatGPT will still ask before `upload_website`. That prompt is ChatGPT's, we cannot turn it off, and it is asking about the one action that sends your code somewhere. Let it ask.

### It says my connection is invalid

Check **Settings → AI connections** in your dashboard. If your connection is listed and says **Signed in**, the connection is fine and the assistant is misreading an error. Tell us what you were doing rather than reconnecting — reconnecting will not fix something that is not a connection problem.

### The code tools are missing

`list_site_files` and `get_site_file` need **an active paid plan**. Not the free trial, and not a plan that has lapsed. Everything else, including uploading a finished website, works on any account.

### I want to disconnect it

**Settings → AI connections → Revoke.** Access stops on the next request; there is no delay and no cache. Revoking does not touch the websites it helped you build.