VibeDeploy MCP server

VibeDeploy MCP Server

Deploy and host AI-built websites on EU infrastructure, straight from your AI agent.

Remote server: https://mcp.vibedeploy.be/mcp (streamable HTTP, OAuth sign-in) Official MCP registry: be.vibedeploy/vibedeploy Website: vibedeploy.be · vibedeploy.eu

What it does

You build a site with your AI (a Claude artifact, a ChatGPT page, a Lovable or Bolt export, a Vite build, plain HTML). VibeDeploy is the missing last step: the agent deploys it to a live HTTPS URL in one tool call, and can keep editing and redeploying it later from the same conversation.

Hosting runs on Kubernetes in Belgium: automatic SSL, custom domains, deploy history with snapshots and rollback, staging, a forms relay for static contact forms, and GDPR-friendly EU data residency by default.

No local install is needed. This is a remote MCP server: you add one URL to your client and sign in once. Every account starts with a 14-day free trial, no card required.

Quick start

Claude Code

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

Claude Desktop / claude.ai

Settings → Connectors → Add custom connector → https://mcp.vibedeploy.be/mcp

Cursor / Windsurf / other MCP clients

{
  "mcpServers": {
    "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" }
  }
}

The first tool call opens a browser window to authorize your VibeDeploy account. After that, try:

"Deploy this site to VibeDeploy and give me the URL."

Tools

38 tools, grouped by what they let the agent do:

Typical flows

• Claude artifact to live URL: Claude builds an artifact, you say "deploy this", the agent ships it and replies with the address. Details: hosting Claude artifacts.
• Localhost project to production: the agent runs your build, deploys the output folder, and the URL outlives your laptop. Details: deploy localhost.
• Custom domain: addcustomdomain plus one CNAME at your registrar; SSL issues automatically.
• Safe iteration: every deploy is snapshotted, so a bad regeneration rolls back in one call.

Notes for client authors and agents

• Transport is streamable HTTP at a single endpoint; authorization is standard OAuth (the server is its own issuer at mcp.vibedeploy.be).
• Large sites: addfiles splits between files, addfile_chunk splits within one file (isFirst / isLast); request bodies are capped at 100 MB.
• The platform also supports a no-MCP path: a single deploy-guide file you paste into any chat AI, which teaches it to publish over plain HTTPS. See what is MCP hosting for how the two paths compare.

Support

Shortened. The full README is on GitHub.