Claude Code workflow

Take Claude Code output live on EU infrastructure

Name: VibeDeploy
Brand: VibeDeploy

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.

Deploy your Claude Code site See pricing

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.

terminal

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.

account_balance

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.

group_work

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
Let the session run to a finished site
Because Claude Code edits your project folder directly, the deployable artefact already exists on disk the moment the agent stops typing; there is no export stage. Plain HTML, Vite, Astro and static Next.js exports are all fair game. Once the local preview holds up, production is one registration command away.
2
Register the VibeDeploy MCP server
A single terminal command does it. Two details save you a retry: every flag must precede the server name, and the transport should be http, since the older SSE variant is deprecated. Appending --scope user registers the server for every project on the machine; leaving the scope at its default limits it to the current project.
```
claude mcp add --transport http vibedeploy https://mcp.vibedeploy.be/mcp
```
3
Authorise the connection once
Open a 14-day trial at vibedeploy.eu; no card is requested. Back inside a Claude Code session, issue the /mcp command and a browser window appears to link the connection to your VibeDeploy account. After that single authorisation, the terminal never needs to hand off to a browser again.
4
Deploy by saying so
Tell the agent to deploy the site to VibeDeploy. It invokes the deploy tool, streams your files up, and the production URL, in the form name.vibedeploy.eu, lands in the same terminal that wrote the code. Repeat after each edit, or instruct the agent to redeploy on its own whenever it finishes a task.
5
Sharing the repo? Commit the config
Teams skip the per-machine add command by checking a .mcp.json file into the repository root. Every collaborator who opens the project in Claude Code inherits the same European deploy target and authorises against their own account.
```
// .mcp.json in the repo root
{
  "mcpServers": {
    "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" }
  }
}
```
6
Move production onto your domain
Site settings take your domain; a CNAME pointed at VibeDeploy completes the link. Certificates issue automatically, most within 60 seconds, and the vibedeploy.eu subdomain keeps answering until yours is ready.

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

It can, because the agent has a shell. Export the magic deploy file from your dashboard and place it in the project; asked to deploy, Claude Code reads those instructions and POSTs the files to VibeDeploy's HTTP API by itself. MCP remains the more comfortable route, but here it is a convenience rather than a requirement.

Which Claude Code projects deploy out of the box?expand_more

Everything that compiles to static or SPA output: hand-written HTML, Vite, Astro, static Next.js exports. What falls outside the model is anything needing a live server, so SSR and API routes stay on a server host while the front-end layer deploys here.

What does --scope user change?expand_more

Scope decides where the registration lives. The default confines the server to the project you ran the command in; --scope user makes it available across every project on the machine, the sensible choice if VibeDeploy is a regular deploy target. Teams standardise differently, with a .mcp.json file committed to the repo.

Can I keep deploying through GitHub instead?expand_more

Yes, and the two coexist. Link the repository in your site settings and each push Claude Code commits sets off a build and redeploy on VibeDeploy's side. That ties releases to git history instead of agent sessions, which some teams prefer for auditability.

The claude mcp add command errors out. What's wrong?expand_more

Check two things before anything else. Flags belong before the server name, not after it, and any snippet mentioning the SSE transport is outdated, since that transport is deprecated. The command in the setup step, with --transport http, is the current form.