Deploy Windsurf sites with VibeDeploy
Windsurf, renamed Devin Desktop in June 2026, builds the project but leaves production hosting to you. Add VibeDeploy to its MCP config, sign in once, and the agent publishes the site to servers in Belgium, connects your domain and can start a database next to it.
Why VibeDeploy for Windsurf
Windsurf's own App Deploys put a preview on a windsurf.build address through Netlify, but only from the legacy Cascade agent, and Windsurf's docs recommend claiming the deployment in your own Netlify account for production apps with sensitive data. VibeDeploy is a production host the current Devin Local agent can reach over MCP: one config entry, a browser sign-in, and every deploy lands on servers in Belgium with your own domain and SSL.
Works with Devin Local and Cascade
VibeDeploy is a remote MCP server, not a Cascade-only feature. Devin Local, a legacy Cascade chat and any other MCP client call the same tools to deploy, edit files, add domains and switch on the forms relay.
A real address, not a preview
Sites start at name.subsite.site and take your own domain with automatic SSL. Every deploy is kept as a version with a restore point before it, so an earlier version is one click away in the dashboard within your plan's restore window.
Room for the backend
When the app needs its own server, Postgres, MySQL or Redis, the agent runs them as containers next to the site with deploy_app, isolated with gVisor: up to 6 services, 2 CPU and 2 GiB of memory per site. Container data is not yet included in snapshots.
How to deploy a Windsurf site
- 1
Know which agent your chat uses
Since the update of 2 June 2026, Windsurf runs as Devin Desktop and new chats use the Devin Local agent; Cascade stays available only for chats you started before. Devin Local reads its MCP servers from the Devin config file, so that is where VibeDeploy goes.
- 2
Add VibeDeploy to mcp_config.json
Open ~/.config/devin/mcp_config.json on macOS or Linux, or %APPDATA%\devin\mcp_config.json on Windows, and add the entry below. With the Devin CLI installed, devin mcp add -s user vibedeploy https://mcp.vibedeploy.be/mcp writes the same entry for you.
{ "mcpServers": { "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" } } } - 3
Sign in when the browser opens
The first time the agent calls a VibeDeploy tool, you are asked to sign in to VibeDeploy in the browser; Google, GitHub or Microsoft is quickest, and a new account starts a 14-day trial without a card. Every client keeps its own login, so a sign-in from Claude Code does not carry over. If VibeDeploy later shows Needs auth in Devin Local's MCP list, click Authenticate next to it; with the Devin CLI, devin mcp logout vibedeploy followed by devin mcp login vibedeploy does the same.
- 4
Ask for the deploy in the chat
Type something like "Build this project and deploy it to VibeDeploy as surf-demo." The agent builds locally, uploads the output and replies with the live address. A follow-up such as "Connect www.example.com to surf-demo" returns the DNS records to set.
- 5
Still on an older Windsurf build?
Cascade in Windsurf versions from before the rename reads ~/.codeium/windsurf/mcp_config.json (%USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows) and expects serverUrl instead of url. Open the file from the MCP section of the Cascade panel and check that the server is switched on.
{ "mcpServers": { "vibedeploy": { "serverUrl": "https://mcp.vibedeploy.be/mcp" } } } - 6
Rather skip MCP?
Link the GitHub repository for a fresh build on every push, or drag the build folder into the VibeDeploy dashboard. The site ends up on the same hosting either way.
Guides for Windsurf
Windsurf hosting at a glance
How Windsurf's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Windsurf default / generic alt | VibeDeploy |
|---|---|---|
| Agent that can deploy | Cascade only (App Deploys) | Devin Local, Cascade or any MCP client |
| Where the site runs | Netlify, under Windsurf's account until claimed | VibeDeploy's servers in Belgium |
| Address | name.windsurf.build | name.subsite.site or your own domain |
| Meant for | Previews (beta) | Production, with versioned deploys |
| Retention | Unclaimed sites may be deleted | Trial ends without a plan: offline, files kept 30 days |
Common questions about deploying Windsurf
Is Windsurf still called Windsurf?expand_more
Not inside the app. Cognition renamed Windsurf to Devin Desktop on 2 June 2026 through a regular update that kept the editor, extensions and settings, and windsurf.com now forwards to devin.ai/desktop. Both names mean the same app, so the steps on this page cover both.
Cascade or Devin Local does not list the VibeDeploy tools. What now?expand_more
Check that the entry sits in the file your agent reads: ~/.config/devin/mcp_config.json with url for Devin Local (Devin versions before v3000.3 read the same mcpServers entry from ~/.config/devin/config.json), or ~/.codeium/windsurf/mcp_config.json with serverUrl for Cascade in an older Windsurf build. Then confirm the JSON is valid and the server is switched on. Cascade holds at most 100 tools across all servers and VibeDeploy brings 40+, so turn off servers you do not need. With Devin Local, ask the agent to list its MCP servers; a new server can take a moment to start.
Why does a browser window open when the agent first deploys?expand_more
That is the VibeDeploy sign-in. The server uses OAuth, so the agent receives its own token and no password or API key ever goes into mcp_config.json. The token is short-lived and refreshed in the background.
How is this different from Windsurf's own App Deploys?expand_more
App Deploys publish a preview to a windsurf.build address on Netlify under Windsurf's account. Windsurf's docs describe them as a beta meant mainly for previews, available only through Cascade, with 1 deploy a day on Windsurf's own Free plan and unclaimed sites that may be deleted. They need no extra account, which is handy for a quick share. VibeDeploy is where the site stays: your own domain, servers in Belgium and room for a backend.
Can the agent deploy a full-stack app from Windsurf?expand_more
Yes. Static builds are served as files, and anything that needs a running process (an API, server-side rendering, Postgres, MySQL, Redis or a worker) runs as a container next to the site through the deploy_app tool, isolated with gVisor. Each site gets up to 6 services, 2 CPU and 2 GiB of memory in total. API keys go into the dashboard under the site's Settings > Secrets, not into the chat, and container data is not yet included in snapshots.
Where is the site hosted, and who runs it?expand_more
On VibeDeploy's own Kubernetes cluster in Belgium, run by Tnet Comm.V, a Belgian company. Site content does not pass through a US processor unless you use the optional AI generation features in the dashboard; all 8 subprocessors are listed on the subprocessors page.
Related deploy guides
Ship your Windsurf project today
14-day free trial, no credit card. Your own domain with automatic SSL. Hosted in Belgium.