# Publish your site with your AI assistant

If you build your site with an AI assistant, Meteor hosts it: your assistant uploads it over **MCP** and it goes live at `https://<name>.metsite.co`. You don't need an API key or to know about servers: you connect the assistant once, ask it to publish and open the link.

Every publish is saved as a **version**. If you don't like a change, you ask your assistant to go back to the previous one, without uploading anything again.

## Step 1 · Connect your assistant to Meteor

Your assistant connects with the address of Meteor's MCP server, which is always the same:

```text
https://api.met.meteor.com.co/api/v1/mcp
```

In Meteor, **Settings → Developers → Connect assistant** gives you the connector name ready to copy (`met-` followed by your workspace identifier) and the steps for each assistant. The full list is in [MCP server](../../mcp.html#conectar).

## Step 2 · Approve the permissions

When you connect, your assistant opens a Meteor window. Sign in and review the list of permissions: among them are **View websites and their versions** and **Publish sites on the internet**. They come in the regular connection; you don't have to ask for them separately. Tap **Authorize**.

- The assistant works on the **workspace you have open in your session**. If you manage several, open the one you want to use first.
- If you connected the assistant before and **Publish sites on the internet** was not on the list, remove its access in **Settings → Developers → Apps**, under **With access to your workspace**, and connect it again.

## Step 3 · Ask it to publish the site

When the site is ready, ask for it in your own words:

- "Publish this site on Meteor with the name panaderia-luz."
- "Upload the new version of the bakery site."

Your assistant does three things:

1. **Checks whether you already have the site.** If it exists, it publishes a new version on that same one; if not, it creates it with the name you gave.
2. **Shows you what it will publish and asks you to confirm.** Meteor requires the assistant to declare that you confirmed it: if it calls without that confirmation, the publish is rejected and nothing is uploaded. In a full publish, what it uploads is what stays on the internet, and what it doesn't upload is no longer there.
3. **Uploads the files and puts the version live.** `index.html` is the home page; `contacto.html` (or `contacto/index.html`) serves `/contacto`, and a `404.html` is shown on routes that don't exist.

The name is the subdomain: 3 to 40 characters, lowercase, with numbers and single hyphens. It is unique across all Meteor sites and some names are reserved by the platform: if the one you asked for is already taken or reserved, your assistant suggests another one.

## Step 4 · See the result and change it

Open `https://<name>.metsite.co`, for example `https://panaderia-luz.metsite.co`. The site goes live with the first published version.

To change it, your assistant doesn't need to have the files at hand, and you don't upload the whole site again:

- "Change the opening hours in the footer of the bakery site."
- "Add a pricing page to the bakery site."

Your assistant reads the file that changes from the live version, edits it and publishes only that one. The rest stays the same, and before publishing it also shows you the change and asks you to confirm.

To undo:

- "Show me the versions of the bakery site."
- "Go back to yesterday's version."

Going back puts an earlier version live without uploading anything. Since it changes what anyone who opens the site sees, your assistant also confirms it with you first.

## Limits

- From the assistant, each publish carries up to **10 MB** in total and **2,000 files**. Images travel encoded and weigh about a third more. Your assistant reads each file of the live site up to 2 MB.
- A site over 10 MB is published from the terminal with the [CLI](cli.html) and an API key with the `sites:write` permission: `met sites deploy dist --site panaderia-luz`. There the zip goes up to 50 MB; the 2,000-file cap is the same.
- Publishing does not consume Energy.
- To publish from your own code, with the SDK or in a pipeline, follow the [static sites](static-sites.html) guide.
