---
title: Use ggui in Claude Desktop
description: Connect Claude Desktop to hosted ggui and get generated UI in your chats in about three minutes — no code, no infrastructure.
---

Claude answers in text. With ggui connected, it can answer with a real interface — a form, a table, a picker — right inside the chat. Setup takes about three minutes and never leaves your browser and Claude Desktop. You don't write any code and you don't open a terminal.

## Step 1: Create your ggui account

Go to [console.ggui.ai](https://console.ggui.ai) and sign in with Google, GitHub, or email. That is your whole signup.

New accounts get **\$5 of free credit** on first sign-in, while the launch grant lasts — it is capped per environment, so if your balance reads \$0.00 a minute after signing in, the cap is exhausted and you top up on `/credits` or add your own model key instead. See [Credits, billing & BYOK](/hosted/billing/). You land on your apps page, and one app is already set up for you. Nothing else to configure here; you can close the tab.

## Step 2: Add ggui to Claude Desktop

In Claude Desktop, open **Settings → Connectors → Add custom connector**, and paste this address:

```
https://mcp.ggui.ai
```

Leave the authentication fields blank, then save. Claude handles the sign-in for you on first use.

## Step 3: Approve the connection

The first time Claude uses ggui — or as soon as you click **Connect** on the new connector card — a browser window opens on the ggui console.

1. Sign in with the same account you created in Step 1.
2. Click **Approve**.

The console creates the access key for you and hands it to Claude Desktop automatically. There is nothing to copy and nothing to paste. The browser window closes on its own, and the connector card shows as connected.

You can see that key later on [the connector keys page](/hosted/connector-keys/). Revoking one is a command-line step for now, and that page walks through it.

## Step 4: Ask for something you'd rather click than type

Open a new chat and ask for something that wants an interface. For example:

> Plan my week — give me a form to rank these five tasks: inbox triage, dentist, Q3 draft, gym, call Mum.

Claude decides an interface is the better answer, asks ggui to build one, and the form appears inline in the chat. It is generated for that request, not picked from a template library.

## Step 5: Use it, and let Claude read your answer

Drag the rows, tick the boxes, hit submit. Your input travels straight back to Claude as structured data, exactly as if you had typed it out — so Claude can act on it in the very next message.

Ask for a variation and you get a new interface. Ask for the same kind of thing again later and it comes back faster, because ggui reuses what it built the first time.

:::note[Running your own server instead?]
Everything above uses hosted ggui at `mcp.ggui.ai`. If you would rather run the server yourself, on your own machine and your own model key, start with the [Self-hosted quickstart](/quickstart/self-hosted/).
:::

## Where to next

- **[Todos playground](/hosted/playgrounds/todos/)** — a live surface to try; one more connector to add, same three-minute ceremony.
- **[Build an agent on hosted ggui](/quickstart/hosted-agent/)** — put generated UI in front of your own users, in your own agent.
- **[The ggui console](/hosted/console/)** — manage your keys, credits, and apps.
- **[Claude Desktop reference](/clients/claude-desktop/)** — other hosts, disconnecting, and what to do if nothing renders.
- **[Trust & security](/hosted/trust/)** — what ggui stores, what reaches a model, and how to delete your account.