English Français العربية

VibeDeploy

Registre officiel Cloud et DevOps

Deploy AI-built sites and apps to EU hosting from your AI agent. OAuth sign-in, 14-day free trial.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http vibedeploy 'https://mcp.vibedeploy.be/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "vibedeploy": {
            "type": "http",
            "url": "https://mcp.vibedeploy.be/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. VibeDeploy MCP Server
  2. What it does
  3. Quick start
  4. Tools
  5. Typical flows
  6. Notes for client authors and agents
  7. Support

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:

AreaTools
Deploydeploy_site, build_and_deploy, deploy_from_url, chunked uploads via begin_deploy / add_files / add_file_chunk / commit_deploy / abort_deploy
Siteslist_sites, get_site, update_site, delete_site, get_site_analytics, check_domain_availability
Filesread_file, read_files, search_files, list_file_hashes, apply_edits, update_file_content, rehost_images
Source of truthlist_source_files, read_source_file, read_source_files, write_source_files, delete_source_file (an editable source tree per site, so agents can do incremental edits and rebuilds)
Domains and DNSadd_custom_domain, list_custom_domains, verify_custom_domain, remove_custom_domain, list_dns_records
Snapshots and historycreate_snapshot, list_snapshots, list_deploys, list_history
Account and formsget_account, get_forms_config, set_forms_config, verify_forms_sender_domain

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: add_custom_domain 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: add_files splits between files, add_file_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

VibeDeploy is operated by Serso BV (Belgium). All hosting layers, control plane, builds and data live in the EU.

Questions fréquentes

Qu'est-ce que VibeDeploy ?

Deploy AI-built sites and apps to EU hosting from your AI agent. OAuth sign-in, 14-day free trial.

Comment installer VibeDeploy ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http vibedeploy 'https://mcp.vibedeploy.be/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour VibeDeploy ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

VibeDeploy est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient VibeDeploy ?

Il est publié par thomasbillen-netizen. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.