Deploy Claude sites with VibeDeploy
Claude builds interactive HTML, React, and SVG artifacts inside a conversation. VibeDeploy turns any artifact into a real site on your own domain, with your branding, your analytics, and EU hosting, in under a minute. With the VibeDeploy MCP server, Claude can deploy it for you without leaving the chat.
Why VibeDeploy for Claude
Claude's built-in publish keeps your artifact on a claude.ai subdomain with an unchangeable Created-with-Claude header. You cannot use a custom domain, control the OG image, favicon, or meta tags, or add analytics, and Anthropic controls the URL and can unpublish it. To own the site you need to move it to real hosting.
Deploy from Claude via MCP
Connect the VibeDeploy MCP server in Claude Desktop or Claude Code, then just say "deploy this." Claude calls the deploy tool directly and hands back your live URL. No copy-paste back to a browser.
Your domain, your branding
Publish on your own domain with no Created-with-Claude header. You control the OG image, favicon, meta tags, and analytics, so the site looks like yours and ranks like yours.
Sub-minute, EU-hosted
Single-file artifacts deploy as-is, no build step. Save the artifact, ship it, add a custom domain in 30 more seconds. Served from Belgium, so visitor data stays in the EU.
How to deploy a Claude site
- 1
Deploy straight from Claude (MCP)
Add the VibeDeploy MCP server to Claude Desktop or Claude Code and sign in once. Then tell Claude to deploy the artifact. It calls the deploy tool, provisions the site, and replies with the live URL. This is the fastest path and needs no manual file handling.
- 2
Or paste the deploy guide into the chat
Not using MCP? Start a 14-day free trial (no credit card), export your VibeDeploy deploy guide from the dashboard, and paste it into the conversation. Claude POSTs the artifact files to the API and returns the URL.
- 3
Or save and drag-and-drop
Download the artifact (or copy the code into index.html), then from the dashboard choose New Site and drag the file in. VibeDeploy serves it as a static site immediately.
- 4
Add a custom domain (optional)
Want artifact.example.com instead of artifact.vibedeploy.be? Point a CNAME at VibeDeploy and add the domain in site settings. SSL provisions automatically, usually within 60 seconds.
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
How is this different from Claude's built-in Publish?expand_more
Claude's Publish gives you a claude.ai URL with a fixed Created-with-Claude header, no custom domain, no control over OG/meta/favicon, and no analytics, and Anthropic can unpublish it. VibeDeploy puts the same artifact on your own domain, with your branding and analytics, on hosting you control.
Do React artifacts deploy without a build step?expand_more
Single-file React artifacts (the in-browser Babel + React UMD pattern) deploy as plain HTML. If your artifact has a real build step (TSX with imports), run npm run build locally first, then deploy the dist folder.
What exactly does the MCP integration do?expand_more
It lets Claude deploy on your behalf. Once the VibeDeploy MCP server is connected, Claude can call deploy, list-sites, add-custom-domain, and other tools directly from the conversation, so you can go from artifact to live URL without touching the dashboard.
What does Publish artifact mean in Claude, and what are its limits?expand_more
Publish creates a shareable claude.ai URL for the artifact. It is useful for a quick demo, but the page keeps Claude's URL and Created-with-Claude header. You cannot attach your own domain or control its OG image, favicon, meta tags, or analytics, and Anthropic can unpublish it. Proper hosting removes those limits.
How do I run a Claude artifact locally instead of hosting it?expand_more
Download the artifact or copy its code into index.html, then open that file in your browser. If it is a project with TSX imports, run npm install and npm run build, then preview the generated dist folder. That local version is only visible on your computer. To give others a stable URL, custom domain, and SSL, deploy the built files to a host.
What about artifact features that need Claude's runtime, like the Mermaid renderer?expand_more
Artifacts that depend on Claude's chat-side rendering need an equivalent client-side library in the deployed file. For Mermaid, include Mermaid.js via CDN in the HTML. Most other artifacts work standalone.
Claude saved my site to /home/workdir/artifacts/index.html. Where is that file?expand_more
That path is inside Claude's own sandbox, not on your computer, and it disappears with the session. To keep the site, download the artifact from the chat (or copy the code into a local file), then deploy that file here. With the MCP server connected, you can skip the download entirely and tell Claude to deploy it for you.
Is building with Claude artifacts vibe coding?expand_more
Yes, it is the purest form of it: you describe what you want and Claude writes the whole page as an artifact. VibeDeploy adds the missing half, vibe deploying: the artifact goes live on your own domain in the same conversation, via MCP or a pasted deploy guide, with no build pipeline.
Related deploy guides
Ship your Claude project today
14-day free trial, no credit card. Custom domain in 60 seconds. Hosted in Belgium.