Take Windsurf output live on EU infrastructure
Devin Desktop, the app that used to be called Windsurf, can write a whole project but has nowhere sovereign to keep it. Register VibeDeploy as an MCP server and its agent ships to infrastructure in Belgium under EU law, attaches your domain and returns a live URL inside the same chat.
Why VibeDeploy for Windsurf
The built-in App Deploys hand previews to Netlify under Windsurf's own account, and only the legacy Cascade agent can trigger them. For work that has to stay in Europe, VibeDeploy gives the agent a different destination through ordinary MCP tool calls: a Belgian operator, servers in Belgium, a public list of 8 subprocessors and a DPA on every paid plan.
Any agent in the app
The connection is plain MCP, so the default Devin Local agent, an older Cascade conversation or another client on the same laptop reach identical deploy, file, domain and form tools.
Jurisdiction you can explain
Hosting runs on a Kubernetes cluster in Belgium, operated by a Belgian company. Customer site content does not pass a US processor unless you use the optional AI generation features.
Databases stay in Belgium too
Postgres, MySQL, Redis or your own server run beside the site as gVisor-isolated containers, started by the agent with deploy_app. The ceiling is 6 services, 2 CPU and 2 GiB per site, and snapshots do not cover container volumes yet.
The Windsurf to production workflow
- 1
Open the right config file
Devin Local, which every new chat has used since the 2 June 2026 update, keeps MCP servers in ~/.config/devin/mcp_config.json (macOS, Linux) or %APPDATA%\devin\mcp_config.json (Windows). Put the VibeDeploy entry there, or let the Devin CLI do it: devin mcp add -s user vibedeploy https://mcp.vibedeploy.be/mcp.
{ "mcpServers": { "vibedeploy": { "url": "https://mcp.vibedeploy.be/mcp" } } } - 2
Authorise your account
Start a 14-day trial on vibedeploy.eu first if you have no account (no card involved). A browser tab then asks you to log in to VibeDeploy the first time a tool runs. Logins are per client, so repeat it in each tool you connect.
- 3
Publish with one instruction
"Deploy this project to VibeDeploy and give me the URL" is enough: the agent builds, uploads and answers with the address. Ask for www.example.com next and it hands back the DNS records to create.
- 4
Working in a pre-rename Windsurf build
Older Windsurf versions run Cascade, which reads ~/.codeium/windsurf/mcp_config.json and needs the key serverUrl in place of url.
{ "mcpServers": { "vibedeploy": { "serverUrl": "https://mcp.vibedeploy.be/mcp" } } } - 5
Without MCP
A connected GitHub repository rebuilds on each push, and the dashboard accepts an uploaded build folder. Both routes land on the same EU infrastructure.
Further reading on Windsurf
Windsurf hosting at a glance
How Windsurf's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Windsurf default / generic alt | VibeDeploy |
|---|---|---|
| Deploy trigger | App Deploys from Cascade | MCP tools from any agent |
| Operator | Netlify via Windsurf's account | Tnet Comm.V, Belgium |
| Purpose | Previews (beta) | Production hosting |
| Own domain | After claiming the site on Netlify | Included, SSL automatic |
Common questions about deploying Windsurf
Windsurf or Devin Desktop: which name applies?expand_more
Both describe one product. Cognition shipped the rename on 2 June 2026 as an ordinary update and kept settings, extensions and the editor; only new chats switched to the Devin Local agent.
The agent cannot see VibeDeploy. Where should I look?expand_more
At the file your agent loads: ~/.config/devin/mcp_config.json (key url) for Devin Local, or ~/.codeium/windsurf/mcp_config.json (key serverUrl) for Cascade on an older build. On a Devin release older than v3000.3, the mcpServers block lives in ~/.config/devin/config.json instead. Broken JSON or a switched-off server hides the tools, and Cascade stops at 100 tools in total, so disable servers you are not using.
Does code or data leave the EU when the agent deploys?expand_more
On the VibeDeploy side, no: files, versions and container data are stored on the cluster in Belgium. Your AI provider is a separate matter, because the model sees whatever passes through the chat under its own terms.
How do Windsurf's App Deploys compare?expand_more
They are a preview tool: Cascade uploads the project to Windsurf's servers and publishes it on Netlify at a windsurf.build address, which you can later claim into your own Netlify account. VibeDeploy is the production side, with your own domain, a DPA on paid plans and servers in Belgium.
Can a database run next to the site?expand_more
Yes. The agent starts Postgres, MySQL or Redis, or your own server, with deploy_app; each runs in a gVisor sandbox on the Belgian cluster. Secrets are entered in the dashboard rather than the chat, and container volumes are not part of snapshots yet.
Is there a staging copy for client review?expand_more
Studio and Business plans add a staging copy of each site at its own address, which you promote to production from the dashboard. For private client previews, Maker and higher can protect a site with a password or invites.
More tool workflows
Put your Windsurf work into production
14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.