Claude workflow

Take Claude output live on EU infrastructure

Name: VibeDeploy
Brand: VibeDeploy

An artifact on claude.ai is a demo. The same file on your own domain, with your analytics, snapshots and EU-hosted infrastructure behind it, is a product page. VibeDeploy is the MCP-connected deploy path that gets it there, and Claude itself can drive the whole publish.

Deploy your Claude site See pricing

Why VibeDeploy for Claude

Publishing on claude.ai leaves the URL, the branding header and the takedown rights with Anthropic, on US infrastructure. Owning the artifact means moving it: your domain, your meta tags, your analytics, hosted under EU jurisdiction. That transfer is a single MCP tool call away once VibeDeploy is connected.

auto_fix

Claude publishes it for you

With the MCP server connected in Claude Desktop or Claude Code, deploying is a sentence. Claude calls the deploy tool, provisions the site and returns the production URL in the same conversation.

language

Full ownership of the page

Your domain, your OG image, favicon, meta tags and analytics snippet. No forced Created-with-Claude header, and nobody upstream can unpublish the site.

timer

EU-hosted, snapshot-backed

Single-file artifacts go live in under a minute on infrastructure inside the EU. Every deploy is snapshotted, so a bad regeneration rolls back in one click.

The Claude to production workflow

1
Let Claude run the deploy over MCP
Once the VibeDeploy MCP server is added to Claude Desktop or Claude Code and authorised once, a single instruction is enough: Claude invokes the deploy tool, provisions the site and posts the live URL back into the conversation. No files change hands manually, and no path is faster.
2
No MCP? Paste the deploy guide
Open a 14-day free trial (no credit card), export the deploy guide from your dashboard, and drop it into the chat. Claude then POSTs the artifact files to the API and reports the resulting URL.
3
Or handle the file yourself
Download the artifact, or copy its code into an index.html, then choose New Site in the dashboard and drag the file in. It is served as a static site the moment the upload lands.
4
Optionally, put it on your own domain
Trade artifact.vibedeploy.eu for artifact.example.com by pointing a CNAME at VibeDeploy and registering the domain in site settings. The SSL certificate typically issues within a minute.

Claude hosting at a glance

How Claude's default hosting and a generic alternative compare to VibeDeploy.

Feature	Claude default / generic alt	VibeDeploy
URL	claude.ai subdomain	Your own domain
Created-with-Claude header	Forced	None
OG image / meta / favicon	No control	Full control
Analytics	None	Yes (your own tags)
Deploy from chat (MCP)	n/a	Yes
Hosting location	US / Anthropic	EU (Belgium)

Common questions about deploying Claude

What do I gain over Claude's own Publish button?expand_more

Ownership. Publish pins the artifact to a claude.ai URL with a fixed Created-with-Claude header, no custom domain, no control over the OG image, meta tags or favicon, no analytics, and Anthropic retains the ability to unpublish it. Deployed here, the identical artifact runs on your domain, with your branding and analytics, on hosting you control.

Is a build step needed for React artifacts?expand_more

Single-file React artifacts, the in-browser Babel plus React UMD pattern, deploy as ordinary HTML with no build at all. Only artifacts with a genuine build pipeline, meaning TSX files with imports, need a local npm run build first; you then deploy the dist folder.

What does connecting the MCP server actually enable?expand_more

It lets Claude act on your account from inside the conversation: deploy, list-sites, add-custom-domain and the other tools become directly callable. The practical effect is going from artifact to live URL without ever opening the dashboard.

When Claude says Publish artifact, what has been published?expand_more

Claude has made the artifact reachable at a claude.ai address for sharing. That is a convenient preview, not independent hosting: Claude's branding remains, your own domain cannot be connected, page metadata and analytics are outside your control, and Anthropic retains the ability to remove it. Moving the file to a host gives you those controls.

Can I test a Claude artifact on my computer before putting it online?expand_more

Yes. Save the artifact as index.html and open it in a browser. For a multi-file project using TSX imports, install its packages, build it locally, and preview the dist output. Only you can reach that local copy. A hosted release is what adds a dependable public address, your domain, and an SSL certificate.

My artifact relies on Claude's chat-side renderer, for example Mermaid. Will it still work?expand_more

Features like that need the equivalent library shipped client-side in the deployed file. For Mermaid, that means including Mermaid.js via CDN in the HTML. Most artifacts have no such runtime dependency and run standalone as-is.

Claude wrote the site to /home/workdir/artifacts/index.html. How do I get it out?expand_more

That location lives inside Claude's temporary sandbox and vanishes when the session ends; nothing was written to your machine. Save the artifact from the conversation, or copy the code out, and deploy the saved file here. Connected over MCP, Claude can deploy it straight from the chat instead.

Where do Claude artifacts fit into vibe coding?expand_more

An artifact is vibe coding's output: a working page written entirely from a plain-language description. What it lacks is a home. Deploying it here completes the loop on European infrastructure, one MCP call from chat to a live URL on your own domain, snapshots included.

Can Claude Code deploy an artifact over MCP as well?expand_more

Yes. The same MCP server serves Claude Desktop and Claude Code. In the terminal, register it once with claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcp, authorise via /mcp, and the agent can publish an artifact file or a whole project folder without leaving the session. The terminal-first workflow has its own guide at /for/claude-code.