Claude Code workflow

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.

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. 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. 2

    Register the VibeDeploy MCP server

    A single terminal command does it. The form below already carries --scope user, which registers the server for every project on the machine; drop that flag and the registration stays with the current project. Keep the transport at http, since the older SSE variant is deprecated.

    claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp
  3. 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. 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. 5

    Sharing the repo? Commit the config

    Teams skip the per-machine add command by checking a .mcp.json file into the repository root. The "type": "http" line matters: Claude Code treats an entry that lacks it as a local stdio server. Every collaborator who opens the project in Claude Code inherits the same European deploy target and authorises against their own account.

    {
      "mcpServers": {
        "vibedeploy": {
          "type": "http",
          "url": "https://mcp.vibedeploy.be/mcp"
        }
      }
    }
  6. 6

    Move production onto your domain

    Site settings take your domain. At your DNS provider, a CNAME aimed at VibeDeploy routes the traffic and a TXT record proves ownership; one click on Verify completes the link. Certificates issue automatically, most within 60 seconds, and the vibedeploy.eu subdomain keeps answering until yours is ready.

Further reading on Claude Code

Claude Code hosting at a glance

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

FeatureClaude Code default / generic altVibeDeploy
Terminal-agent integrationDepends on the host (CLI or MCP server)Native MCP server
Hosting locationVariesEU (Belgium)
Framework auto-detectYes (Vercel/Netlify)Runs npm run build and finds the output folder
Redeploy on git pushVariesYes
Steps from code to liveHost account plus CLI, MCP or repo setupOne MCP command, then one sentence

Common questions about deploying Claude Code

Is Claude Code able to put a site live on its own?expand_more

It is, as soon as VibeDeploy is registered as an MCP server. One terminal command handles that: claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp. Next, type /mcp inside a session and approve the connection in your browser; a trial account without a card will do. Ask for a deploy in plain words and the agent ships the build to the Belgian cluster, then reports the production URL in the same session.

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 store it where git will not pick it up, since it carries a private deploy key; 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. Work that needs a live process, such as SSR or API routes, no longer has to move to another host: the deploy_app tool runs it as a container beside the front end, as the backend question explains.

My Claude Code project has a backend. Can that run in the EU as well?expand_more

Yes, beside the front end on the same site. Through the deploy_app MCP tool the agent starts containers from any public image: the server it wrote, a Postgres or MySQL database, Redis, background workers. The ceiling per site is six services sharing 2 CPU and 2 GiB of memory, each sandboxed with gVisor on infrastructure in Belgium. Credentials are entered in the dashboard (the site's Settings, Secrets section), never pasted into the session. One gap today: snapshots do not cover container data yet.

Why choose this over Vercel when deploying from Claude Code?expand_more

Not for reach. Vercel serves from 126 points of presence in 51 countries, maintains Next.js and runs it without configuration, and its own MCP server can deploy from the terminal too. The case for VibeDeploy is jurisdiction and scope: production stays in a single region in Belgium under a Belgian operator, each plan has a fixed price starting at EUR 4 a month, and form handling, password protection (from Maker) and backend containers sit on the same site.

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

Start by setting your command next to the one in the setup step. A snippet that still names the SSE transport is outdated, since that transport is deprecated; --transport http is the current form. Teams configuring through .mcp.json should check that the entry carries "type": "http", because Claude Code otherwise interprets it as a local stdio server. With the server in place, /mcp inside a session completes the sign-in.

More tool workflows

Put your Claude Code work into production

14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.