Deploy Claude Code

Deploy Claude Code sites with VibeDeploy

Claude Code is Anthropic's coding agent that lives in your terminal and writes files straight into your project folder. The code is already on your disk; what's missing is a place to put it live. VibeDeploy connects over MCP with a single command, and from then on "deploy this site" gets you an EU-hosted URL with SSL, straight from the same terminal.

Why VibeDeploy for Claude Code

Claude Code ends every session the same way: a finished site sitting in a local folder. The usual next move is pushing to GitHub and wiring up Vercel, Netlify, or Cloudflare, which means a second platform to configure before anyone sees your work. VibeDeploy shortens that to one step. The agent that wrote the code deploys it too, over MCP or the plain HTTP API, to hosting in Belgium.

cable

Connected in one command

Claude Code is a native MCP client. Run claude mcp add once in your terminal and the agent gains VibeDeploy's deploy, domain, container and site-management tools. No extension, no separate CLI to learn.

alt_route

Two agent-driven deploy paths

MCP is the smooth road, but Claude Code also has shell access. Give it the magic deploy file from your dashboard and it can POST your files to VibeDeploy's HTTP API directly, no MCP setup at all.

shield_lock

Belgian hosting, no metering

Your site is served from Belgium with automatic SSL and a custom domain on every plan. Flat per-plan pricing, so letting the agent redeploy twenty times a day costs exactly nothing extra.

How to deploy a Claude Code site

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

    Add the VibeDeploy MCP server

    Run this once. --scope user makes the server available in every project on your machine; leave it out and Claude Code registers it for the current project only. Stick with the http transport: the older SSE transport is deprecated.

    claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp
  3. 3

    Authorise once with your account

    Start a 14-day free trial at vibedeploy.be (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. 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.subsite.site. Ask again after every edit, or tell it to redeploy on its own when it finishes a task.

  5. 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. Keep the "type": "http" line: without a type, Claude Code reads the entry as a local stdio server. Everyone who opens the project in Claude Code gets the same deploy target and authorises with their own account.

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

    Put it on your own domain

    Add your domain in site settings, then set the DNS records the dashboard shows: a CNAME pointing at VibeDeploy and a TXT record that proves the domain is yours. Click Verify and SSL provisions automatically, usually within 60 seconds. Until then the site stays reachable on its vibedeploy.be subdomain.

Guides for 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

Can Claude Code deploy a website?expand_more

Yes. Register VibeDeploy once with claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp, then run /mcp in a Claude Code session and sign in with your VibeDeploy account in the browser window that opens (a 14-day trial without a card is enough). After that, say "deploy this" and Claude Code uploads the site and prints the live URL in the terminal.

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, keep it outside the repository or list it in .gitignore (it contains a private deploy key), 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 deploys as is: plain HTML, Vite, Astro, or a static Next.js export. A project that needs a running server, such as server-side rendering or API routes, can run in a container next to the site through the deploy_app tool (see the backend question below).

Where should I host a Claude Code app with a backend?expand_more

On the same site. Static files and single-page apps are served directly, and the backend runs in containers next to them: your own server from the source tree, Postgres, MySQL, Redis or workers, from any public image. Claude Code starts them with the MCP tool deploy_app, up to 6 services with 2 CPU and 2 GiB of memory in total, isolated with gVisor. API keys go in the dashboard (site Settings > Secrets), never in the chat. Container data is not yet included in snapshots.

How does this compare to deploying to Vercel from Claude Code?expand_more

Both work from the terminal: Vercel has a CLI and its own MCP server that can deploy as well. The difference is where the site runs and what comes with it. VibeDeploy runs on its own cluster in Belgium, operated by a Belgian company, at a flat price per plan from EUR 4 a month, with a forms relay, password-protected sites (Maker and up) and backend containers on the same site. Vercel is stronger on reach and Next.js: it maintains Next.js, deploys it with zero configuration and serves sites from 126 points of presence in 51 countries, while VibeDeploy runs in one region.

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

Compare it with the command in the setup step, character for character. The usual culprit is an old snippet that uses the SSE transport, which is deprecated: use --transport http. If you configured the server in .mcp.json instead, the entry needs "type": "http", because Claude Code reads an entry without a type as a local stdio server. Once the server is added, run /mcp in a session to sign in.

Related deploy guides

Ship your Claude Code project today

14-day free trial, no credit card. Your own domain with automatic SSL. Hosted in Belgium.