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

# Quickstart

> Build and publish your first Zite app with your favorite AI agent.

Your agent runs on a cloud sandbox with your workspace's code, writes the app, and publishes it — no local
setup on your end.

<Info>
  A **workspace** is a Zite database plus the apps built on it. See [Workspaces](/concepts/workspaces).
</Info>

## 1. Connect the Zite MCP

Add the Zite MCP server to your AI tool and authorize it. The MCP URL:

```text theme={null}
https://mcp.zite.com/mcp
```

<CodeGroup>
  ```bash Claude Code theme={null}
  claude mcp add --transport http zite https://mcp.zite.com/mcp
  # then run /mcp, select zite, and choose Authenticate
  ```

  ```text Claude theme={null}
  Settings → Connectors → Add custom connector
  Name: Zite
  URL:  https://mcp.zite.com/mcp
  ```

  ```text ChatGPT theme={null}
  Open the Zite app from the ChatGPT apps directory,
  click Connect, and authorize.
  (Available on paid ChatGPT plans.)
  ```

  ```text Cursor theme={null}
  MCP settings → add a server
  URL:       https://mcp.zite.com/mcp
  Transport: HTTP (streamable)
  Auth:      OAuth
  ```
</CodeGroup>

On first connect you sign in and authorize access. The agent then acts as **you** — it can only see and
change workspaces you have access to. Using VS Code, Codex, Windsurf, Zed, or another client? See the
per-tool steps in [Connect](/mcp/connect).

## 2. Describe what you want to build

Tell the agent the system you want — be specific about the data and the screens:

```text theme={null}
Build a support-ticket app in a new workspace called "Helpdesk". Tickets have a
subject, description, status (open / in progress / closed), priority, and an
assignee.
```

The agent spins up the workspace — a fresh database — and a cloud sandbox, then designs the tables,
scaffolds the app, writes the React UI and backend [workflows](/concepts/workflows), and iterates
until it type-checks and runs — the [build loop](/mcp/build-loop), which you can watch live in the editor.

Already have a workspace? Name it in your prompt and the agent builds into it instead of creating one.

## 3. Choose who can access it

New apps are **internal** by default — only your Zite organization can open them. To make an app public, ask
the agent to set it **external**, which adds a sign-in screen (email, Google, or SSO). See
[Authentication](/concepts/authentication).

## 4. Publish

```text theme={null}
Publish the app.
```

External apps go live at `https://<subdomain>.zite.so`; internal apps become available to your team. Add a
custom domain or roll back any time — see [Publishing](/deploy/publishing).

Next: [how building works](/mcp/overview) and [the database client](/framework/database-client).