Take Claude Code output live on EU infrastructure
Every Claude Code session ends with working files on local disk and an open question about where they should run. Registering one MCP server answers it permanently: the agent carries each build onto infrastructure inside the EU, attaches your domain, and reports the production URL back into the session it came from.
Why VibeDeploy for Claude Code
The well-worn pipeline is Claude Code to GitHub to an American hosting platform: three tools where one would do, with production traffic settling under US jurisdiction almost by accident. VibeDeploy collapses that chain. Deploys become MCP tool calls, or plain HTTP API calls when you skip MCP entirely, and they terminate on servers in Belgium run by a European operator. GitHub build-on-push remains available for teams that want it; it just stops being a requirement.
The terminal is the whole pipeline
Writing, previewing, deploying, attaching a domain: with VibeDeploy's tools registered over MCP, Claude Code does all of it in a single session. There is no second platform to configure and no dashboard detour between code and production.
Jurisdiction settled at deploy time
Each deploy lands on EU infrastructure in Belgium, operated by a European company. For client work and GDPR-sensitive projects, where the site runs is decided the moment the agent ships it, not renegotiated later.
Setup that travels with the repo
A .mcp.json file in the project root gives every collaborator's Claude Code the same European deploy target, each authorising with their own account. Flat per-plan pricing means the shared workflow never inflates the bill.
The Claude Code to production workflow
- 1
Finish the site in your terminal
Claude Code writes files directly into your project folder, so there is nothing to export or download. Any static setup works: plain HTML, Vite, Astro, or a static Next.js export. When the local preview looks right, you are one command away from live.
- 2
Add the VibeDeploy MCP server
Run this once. All flags go before the server name. Add --scope user to make the server available in every project on your machine; without it, the default scope registers it for the current project only. Stick with the http transport, the older SSE transport is deprecated.
claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcp - 3
Authorise once with your account
Start a 14-day free trial at vibedeploy.eu (no credit card). Then, inside a Claude Code session, run the /mcp command. A browser window opens so you can authorise the connection with your VibeDeploy account, and that's the last time you leave the terminal.
- 4
Ask for a deploy in plain language
"Deploy this site to VibeDeploy." Claude Code calls the deploy tool, uploads your files, and prints the live URL right in the terminal, something like name.vibedeploy.eu. Ask again after every edit, or tell it to redeploy on its own when it finishes a task.
- 5
Working in a shared repo? Check in .mcp.json
For a project-scoped setup that travels with the code, put a .mcp.json file in the repo root instead of running the add command per machine. Everyone who opens the project in Claude Code gets the same deploy target and authorises with their own account.
// .mcp.json in the repo root { "mcpServers": { "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" } } } - 6
Put it on your own domain
Add your domain in site settings and point a CNAME at VibeDeploy. SSL provisions automatically, usually within 60 seconds. Until then the site stays reachable on its vibedeploy.eu subdomain.
Claude Code hosting at a glance
How Claude Code's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Claude Code default / generic alt | VibeDeploy |
|---|---|---|
| Terminal-agent integration | None / manual | Native MCP server |
| Hosting location | Varies | EU (Belgium) |
| Framework auto-detect | Yes (Vercel/Netlify) | Yes |
| Redeploy on git push | Varies | Yes |
| Steps from code to live | Repo + host setup | One sentence to the agent |
Common questions about deploying Claude Code
Can Claude Code deploy without the MCP server?expand_more
Yes. Claude Code runs shell commands, so it can talk to VibeDeploy's HTTP deploy API on its own. Export the magic deploy file from your dashboard, drop it in the project, and ask the agent to deploy: it reads the instructions and uploads the files itself. MCP is more comfortable, but it is genuinely optional here.
Which Claude Code projects deploy out of the box?expand_more
Anything that produces static or SPA output: plain HTML, Vite, Astro, or a static Next.js export. Server-side rendering and API routes need a running server, which is outside VibeDeploy's static model, so keep SSR projects on a server host.
What does --scope user change?expand_more
By default, claude mcp add registers the server for the current project only. With --scope user it becomes available in every project on your machine, which is what you want if you deploy to VibeDeploy regularly. For a team-wide setup, use a .mcp.json file in the repo instead.
Can I keep deploying through GitHub instead?expand_more
Of course. Connect the repo in your site settings and every push Claude Code commits triggers a fresh build and redeploy on VibeDeploy. Handy when you want deploys tied to your git history rather than to agent sessions.
The claude mcp add command errors out. What's wrong?expand_more
The two usual culprits: flags placed after the server name (they must come before it), or an old snippet using the SSE transport, which is deprecated. Use --transport http exactly as shown in the setup step.
Put your Claude Code work into production
14-day free trial, no credit card. Domains, staging and snapshots included. Runs on EU infrastructure.