Vibedeploy

What vibedeploy MCP server does

The vibedeploy MCP server connects an AI client to VibeDeploy, a hosting platform operated from Belgium. It is intended for sites produced by AI workflows, including Claude artifacts, ChatGPT pages, Lovable or Bolt exports, Vite builds, and plain HTML. An agent can publish a site to a live HTTPS address, then continue changing and redeploying it from the same conversation.

Hosting includes automatic SSL, custom-domain support, deployment history, snapshots, rollback, staging, and a forms relay for static contact forms. The README states that hosting layers, the control plane, builds, and data are located in the EU. Every account begins with a 14-day trial without requiring a payment card.

How it works

The service is remote rather than a package that runs on the developer’s machine. MCP clients connect to https://mcp.vibedeploy.be/mcp using streamable HTTP. Authorization uses OAuth, with VibeDeploy acting as the issuer. On the first tool call, the client opens a browser for account authorization; subsequent calls use that authorization.

A simple workflow is to give the agent a finished site and ask it to deploy the site. For larger projects, files can be sent in batches or split into chunks within an individual file. The request body limit is 100 MB. VibeDeploy also maintains an editable source tree for each site, allowing agents to read, modify, and rebuild source files over multiple iterations.

Setup and configuration

Add the remote endpoint to an MCP-compatible client. Claude Code can register it with:

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

Claude Desktop and claude.ai can use the same URL as a custom connector. Cursor, Windsurf, and other MCP clients can configure a server named vibedeploy with that URL. No environment variables or local installation are described as necessary. Sign in through the browser prompt when the first tool call requests authorization.

Tools and capabilities

The vibedeploy MCP server exposes 38 tools across several areas:

• Deployment tools publish a site directly, build and deploy it, deploy from a URL, or manage chunked uploads with begin, add, commit, and abort operations.
• Site tools list, inspect, update, delete, and analyze sites, and check whether domains are available.
• File tools read, search, hash, edit, update, and rehost images. Source-tree tools separately list, read, write, and delete editable source files.
• Domain tools add, list, verify, and remove custom domains, and list DNS records. SSL is issued automatically after the custom-domain setup described by the project.
• History tools create snapshots and inspect snapshots, deployments, and history for rollback-oriented workflows.
• Account and forms tools retrieve account or forms configuration, update forms settings, and verify a forms sender domain.

Limitations and notes

The service requires an MCP client that supports its remote streamable-HTTP endpoint and OAuth authorization. The provided material does not describe a local or self-hosted mode for this MCP server. Large transfers must account for the 100 MB request-body cap and use the available file or file-chunk operations when needed.

Custom domains require adding a CNAME at the registrar in addition to calling the domain tools. The README also describes a separate, non-MCP deployment-guide approach for publishing over plain HTTPS, but that is an alternative path rather than a capability of this MCP connection.