What is MCP hosting? Deploying a site via MCP
MCP hosting lets an AI agent deploy your site to a live URL, no manual upload. How deploy-via-MCP works and how to connect it in Claude, Cursor or Windsurf.
Short answer
MCP hosting means your AI agent publishes and manages a website through the Model Context Protocol instead of you uploading files. You add the host's MCP server to Claude, Cursor or another client once and sign in (for ChatGPT, that takes a plan with write access for custom MCP servers). From then on the agent can deploy, read, edit and redeploy the site from the chat. VibeDeploy's server lives at https://mcp.vibedeploy.be/mcp.
Let your AI deploy it
Connect VibeDeploy to Claude or Cursor once (ChatGPT on plans with MCP write access); your agent publishes and updates the site. 14 days free, no card.
https://mcp.vibedeploy.be/mcpMCP hosting means deploying and managing a website through the Model Context Protocol, so an AI agent like Claude, Cursor or Windsurf can publish your site to a live URL without you uploading anything by hand. In practice you connect a hosting provider's MCP server to your AI client once, then tell the agent "deploy this site" in plain language: it ships the files, returns the public URL, and can read, edit and redeploy later. VibeDeploy runs this at https://, and the VibeDeploy MCP server setup page has one-click install buttons and the steps for every client.
Below is what MCP is, why deploying through it differs from a normal deploy, and the exact setup.
What is MCP?
The Model Context Protocol (MCP) is an open standard, introduced by Anthropic in November 2024 and now supported across many AI clients, that lets an AI assistant call external tools through a consistent interface. Instead of only generating text, an assistant connected to an MCP server can take real actions: query a database, read a file, or, in our case, deploy a website.
An MCP server publishes a set of named tools with descriptions. The AI reads those descriptions and decides which tool to call based on what you asked. When you say "put this online", a well-described deploy tool is what the agent reaches for.
What "MCP hosting" adds over a normal deploy
A normal deploy means you build your site, open a dashboard and upload, or you push to Git and wait for CI. MCP hosting folds that into the conversation you are already having with your AI tool:
- No context switch. You stay in Claude or your editor. The agent deploys; you do not switch to a dashboard.
- No re-typing steps. The agent already has your files. It calls the deploy tool with them directly.
- Round trips. The agent can read the live site back, make an edit and redeploy, all in one chat. "Fix the nav and ship it" becomes a single instruction.
- Plain language. You never learn a CLI or a YAML format. The tool descriptions do the matching.
This is why deploying through MCP fits AI-built sites so well: the same agent that wrote your site can put it online.
How to deploy a site via MCP with VibeDeploy
The setup is one-time. After that, deploying is a sentence.
Step 1: add the server to your AI client
The server address is https://. Where it goes depends on the client:
- Claude (web, Desktop and mobile): Customize > Connectors, then + Add > Add custom connector. Name it VibeDeploy, paste the URL and click Continue. Keep the detected settings (if Claude asks for an OAuth client, choose Register automatically) and click Add.
- Claude Code: run
claude mcp add --transport http --scope user vibedeploy https://, thenmcp.vibedeploy.be/ mcp /in a session to sign in.mcp - Cursor: add the server to
~/(or.cursor/ mcp.json .cursor/for one project). Remote servers take amcp.json url:
{
"mcpServers": {
"vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" }
}
}- Windsurf: since June 2026 Windsurf is called Devin Desktop, and its Devin Local agent reads the same
urlentry from~/(on Windows.config/ devin/ mcp_config.json %APPDATA%\devin\mcp_config.json). Older Windsurf builds, with the Cascade agent, read~/and want.codeium/ windsurf/ mcp_config.json serverUrlinstead ofurl:
{
"mcpServers": {
"vibedeploy": { "serverUrl": "https://mcp.vibedeploy.be/mcp" }
}
}The guides for Cursor, Windsurf and Claude Code walk through each client in more detail, and the MCP server page covers ChatGPT, VS Code, Codex and Gemini CLI too.
Step 2: sign in once
A browser window opens so you can sign in to VibeDeploy and approve the connection. This uses OAuth, so your agent gets its own access token, not your password. No account yet? The same window creates one, with a 14-day trial and no card.
Step 3: tell the agent to deploy
Ask in plain language:
Deploy this site to VibeDeploy.
The agent calls the deploy tool, uploads your build, and replies with the live URL at yourname.subsite.site. To iterate later: "read the homepage, fix the footer link and redeploy." It all happens in the chat.
Step 4: add a custom domain (optional)
Ask the agent to add your domain, or do it in the dashboard. Set the DNS records it gives you and SSL is issued automatically.
Let your AI deploy it
Connect VibeDeploy to Claude or Cursor once (ChatGPT on plans with MCP write access); your agent publishes and updates the site. 14 days free, no card.
https://mcp.vibedeploy.be/mcpIs deploy-via-MCP safe?
Yes, with the usual care. VibeDeploy's MCP server uses OAuth 2.1 with PKCE and a consent screen, so you approve access explicitly, and the agent's token only reaches the sites of your own team. Tools that replace or delete live files are marked as destructive. Deleting a site, or replacing every file of an existing site with deploy_site, needs an explicit confirmation; update_site and build_and_deploy can replace all files without one, so review their calls before you approve them. To end the access, remove the connector in your AI client.
What MCP hosting can and cannot do
MCP hosting is not limited to static files. Static sites and single-page apps are served directly. A site can also run containers next to it (your own server, Postgres, MySQL, Redis or workers; up to 6 services with 2 CPU and 2 GiB in total), deployed by your AI through the MCP tool deploy_app and isolated with gVisor. Container data is not yet included in snapshots, and container logs reach you through the agent (get_app_status) because the dashboard has no log view yet. API keys and other secrets go into the dashboard under the site's Settings > Secrets, never into the chat.
What it does not do: replace your editor or your AI tool. It is the publish step, wired into the tools you already use. There is also no restore tool over MCP. The agent can take a snapshot before a risky change, but going back to an earlier version is one click in the dashboard, within your plan's restore window.
Where this fits
Deploying through MCP is one of several ways to ship to VibeDeploy. You can also drop a ZIP or build folder into the dashboard, connect GitHub to build on every push, or paste the deploy guide into a chat AI that cannot connect to MCP servers. See localhost to live URL for the manual path, the tool-by-tool guides for your specific client, and the pillar guide, How to deploy AI-built websites in 2026, for the full picture.
Ready to try it? Create your account, connect the MCP server, and tell your agent to deploy.
Sources
- Anthropic, "Introducing the Model Context Protocol", 25 November 2024: https://www.anthropic.com/news/model-context-protocol
- Claude Help Center, custom connectors using remote MCP: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp
- Cursor docs, Model Context Protocol (config locations and the
urlkey): https://cursor.com/docs/mcp - Devin Desktop FAQ (Windsurf renamed Devin Desktop on 2 June 2026): https://docs.devin.ai/desktop/devin-desktop-faq
- Devin CLI MCP configuration (the Devin Local config file): https://docs.devin.ai/cli/extensibility/mcp/configuration
- Devin CLI configuration import (Windsurf's
~/): https://docs.devin.ai/cli/reference/configuration/read-config-from.codeium/ windsurf/ mcp_config.json
All pages read on 13 October 2026.
Ship your AI-built site in minutes
VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.
Deploy guides for this topic
Questions people ask
Is MCP hosting the same as hosting an MCP server?
No. Here the hosting company runs the MCP server and your agent uses it to publish your website. Running your own MCP server is a different job: it needs a host for a long-running process, which on VibeDeploy would be a container next to a site, started with deploy_app.
Which AI tools can deploy a website through MCP?
Any client that supports remote MCP servers with OAuth: Claude on the web, Desktop and mobile, Claude Code, Cursor, VS Code with GitHub Copilot, Windsurf (now Devin Desktop), OpenAI Codex and Gemini CLI, plus ChatGPT on plans that allow write access for custom MCP servers. The VibeDeploy MCP server page has the setup for each.
Can the agent deploy a backend, not just a static site?
Yes. Static sites and single-page apps are served directly, and the deploy_app tool runs containers next to a site: your own server, Postgres, MySQL, Redis or workers, isolated with gVisor, up to 6 services with 2 CPU and 2 GiB in total. Container data is not yet included in snapshots.
Do I need to pay to try it?
No card is needed to start. A new VibeDeploy account gets a 14-day trial with one site and one custom domain you already own. Plans start at EUR 4 a month.
Related reading
How to Deploy AI-Built Websites in 2026: The Complete Guide
Every way to get an AI-built site live in 2026: MCP deploys, a deploy guide for any chat AI, upload or GitHub, containers, and a 25-tool export matrix.
"Uploads the file below from this task to claude.ai": Claude's Publish Artifact Prompt Explained
What Claude's Publish artifact prompt means: "Uploads the file below from this task to claude.ai", who can see the page, the three variants, and how to undo it.
Claude Artifact Won't Publish or Share? Causes and Fixes
Why a Claude artifact won't publish or share: Claude accounts, admin settings, the 16 MiB limit, the renamed button. How to unpublish, and the fix.
Deploy a Website From Claude With One Custom Connector
Add VibeDeploy as one custom connector in Claude on the web, Desktop, mobile or Cowork, then let Claude publish your site and connect your domain.