Updated 6 min readBy The VibeDeploy team

ChatGPT or Claude chat to a live European site

The site exists in a chat window; a real domain is the unfinished step. Two handoffs, the deploy guide and MCP, take a chat-built site live on EU hosting.

Finish the job in the same chat

Paste the deploy guide into ChatGPT or connect Claude once, and your assistant publishes the site on servers in Belgium. 14 days free, no card.

There is a moment in every chat-built website project where the interesting part ends and the awkward part begins. The AI has produced the pages, the copy reads well, the preview looks right. Then the conversation stalls on a question the chat cannot answer by itself: how does this become a real site, on a real domain, that stays up after the tab closes?

Most guides answer with a detour through developer tooling: install a CLI, create a repository, configure a pipeline. For someone who built the site by describing it in sentences, that detour is where projects die. The better answer is to let the same conversation finish the job. There are two ways to do that on VibeDeploy, and which one you use depends on what kind of AI client you are talking to.

Handoff one: the deploy guide, for plain chat tools

ChatGPT, Claude in the browser, Gemini and similar assistants can write code, and some of them can also make web requests from inside the conversation. None of them knows how a particular host wants to receive files. The deploy guide fixes that: it is a single instruction file from your VibeDeploy dashboard that teaches the AI exactly how to publish your site, in one paste.

The flow looks like this:

  1. You paste the deploy guide into the conversation, alongside the site the AI already built.
  2. If the assistant can make network requests, it packages the files and sends them to the deploy endpoint itself. If its sandbox has no network access, it builds a deploy page instead, which you open in your browser to finish the upload, with download and copy options as a fallback.
  3. You get a live URL on EU infrastructure, with HTTPS already active.

No copying files out of a code block into a folder structure you have to guess at. The tool-specific walkthroughs for ChatGPT, Claude artifacts and Gemini show the exact prompts, but the principle is identical everywhere: the guide is the bridge, the AI does the crossing.

One detail worth knowing: the guide tells the AI to send only the site name and the files, and to deploy to the live site unless you explicitly ask for staging. Assistants like to be helpful by adding settings nobody asked for, and the guide is written to prevent that.

If the site was built with ChatGPT Sites rather than in a plain chat, read ChatGPT Sites and GDPR first: it covers what OpenAI says about where Sites data lives, and how to move the same site to an EU host.

Handoff two: MCP, for agent clients

If you work in Claude Desktop, Cursor, Windsurf or another client that supports the Model Context Protocol, the handoff gets tighter. Instead of pasting instructions per project, you connect the VibeDeploy MCP server once, at https://mcp.vibedeploy.be/mcp, and authorise it against your account through OAuth. From then on the agent has deployment as a native capability. Setup per client is on the MCP page.

The difference in day-to-day use is iteration. With the deploy guide, publishing is an event at the end of a conversation. Over MCP, it is a verb inside it: the agent can list your sites, read what is live, apply an edit, and redeploy, all as steps in the same exchange. "Tighten the hero copy and ship it" is a complete instruction. The Cursor and Windsurf guides cover the short client configuration.

What happens on the European side

Either handoff lands in the same place. The files are deployed to VibeDeploy's own Kubernetes cluster in Belgium, operated by a Belgian company, Tnet Comm.V, and served from an isolated environment per site. TLS certificates are issued automatically. The platform subdomain is live immediately. For your own domain you add it, set the DNS records the dashboard shows, and wait for the check to pass; over MCP the agent can do that part too, with add_custom_domain and verify_custom_domain. The 14-day trial already lets you link one domain you own.

For a site aimed at European visitors or customers, this matters beyond latency. The hosting, the deployment history and the account data stay with a Belgian company on servers in Belgium, and the few exceptions are named on the public sub-processor list. The compliance questions that follow a public launch, where is it hosted, who operates it, is there a DPA, have short answers. The background on why that is worth deciding deliberately is in data sovereignty for AI-built websites.

Iterating after launch

A chat-built site is rarely finished at first deploy, and the workflow holds up past launch:

  • In-chat edits. Over MCP, the agent reads the deployed files, changes them, and redeploys. The site in production is the working copy.
  • Staging. On Studio and Business, changes can go to a testing copy at its own address first and be pushed live when they look right.
  • Restore points. A restore point is taken before every deploy, and you can bring back an earlier version in one click from the dashboard within your plan's window: 3 days on the trial, Solo and Maker, 7 on Studio, 30 on Business. The agent can make an extra restore point before a risky edit with create_snapshot; the restore itself is a click for you, because there is no restore tool over MCP.

If your project lives on your own machine rather than in a chat, the same platform accepts a dragged-in build folder; that path is documented at deploy localhost to production.

Cost and the honest limits

Plans are flat: 4, 15 or 39 euro per month depending on scale, prices including VAT where it applies, with a 14-day trial that needs no credit card. Details on the pricing page.

The limits to be clear about: static sites and single-page apps are served directly, and a site can also run containers next to it (your own server, Postgres, MySQL, Redis or workers; up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app and isolated with gVisor. Container data is not yet included in snapshots. A chat-built marketing site, portfolio or dashboard fits easily; a project that needs more than those container limits, or a global edge network, is better off elsewhere. Everything runs in one region, Belgium.

The gap between "the AI built it" and "it is live in Europe" used to be the hard part of these projects. With the deploy guide for chat tools and MCP for agents, it is now the shortest step in the conversation.

From the VibeDeploy team

Ship your AI-built site in minutes

VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.

Deploy guides for this topic

Related reading