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.

Deploy your Claude Code siteSee pricing

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, 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. 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. 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.vibedeploy.be. 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. 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. 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.be subdomain.

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 integrationNone / manualNative MCP server
Hosting locationVariesEU (Belgium)
Framework auto-detectYes (Vercel/Netlify)Yes
Redeploy on git pushVariesYes
Steps from code to liveRepo + host setupOne 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.

Ship your Claude Code project today

14-day free trial, no credit card. Custom domain in 60 seconds. Hosted in Belgium.

Start free trialCompare plans