Let Cascade publishwhat it just built
Windsurf has native MCP support, so dplooy plugs straight into Cascade. Ask it to deploy the folder on your disk and a live HTTPS URL comes back in the same reply.
Building and shipping shouldn't be separate tools
Cascade can write the whole site. Getting it in front of a human still usually means a browser tab, a login and a drag-and-drop.
The usual detour
- localhost works for exactly one person
- Sharing means pushing to git first, even for a throwaway
- Every host wants its own CLI and its own account
- You leave the editor and lose the thread
- Nothing tells you if anyone opened it
With dplooy connected
- Cascade deploys the folder it just built, from the panel
- A real HTTPS URL in the same reply
- No repo required for something short-lived
- Analytics, SEO tooling and a visual editor included
- Redeploy the same project and the URL never moves
One config block, then you're done
Get an API key
In dplooy, go to Settings → API Keys and create one. It starts with dpk_live_. The local MCP server uses it to act on your account, so treat it as a credential and keep it out of anything you commit.
Open Windsurf's MCP config
In Windsurf Settings, go to the Cascade tab, find the MCP Servers section and choose View raw config. That opens mcp_config.json — on Windows it lives under %USERPROFILE%\.codeium\windsurf\, and on macOS and Linux under ~/.codeium/windsurf/. Create the file if it isn't there; Windsurf doesn't write one on first launch.
Add the dplooy server
Inside the mcpServers object, add an entry named dplooy that runs npx -y @dplooy/mcp-server with DPLOOY_API_KEY in its env block. Same shape as every other MCP server in that file. Reload Windsurf and the tools show up in Cascade.
Ask Cascade to deploy
"Build this and deploy it to dplooy as my-site." The server runs locally, so it can read the folder that already exists on your disk and push the whole thing up — no zipping, no upload dialog, no context switch.
Deploy the build output, not the source
Dplooy serves static files. A folder containing vite.config.ts and a src directory is source code — we reject it with an explanatory message rather than hosting a broken site. Run the build first and deploy dist (or out for a Next.js static export, build for Create React App). Tell Cascade that once and it will build before deploying from then on.
What the deployed project gets
Every site gets the same treatment, whether a person uploaded it or an agent did.
Your own subdomain
yourname.dplooy.com instead of a link that names somebody else's product. Point a custom domain at it on Pro.
Free SSL, always on
Every site is served over HTTPS with a certificate we manage. Nothing to buy, configure or renew.
Real analytics
Views, unique visitors, countries, referrers and devices — for the whole site, exported as CSV whenever you want it.
Findable in search
robots.txt and sitemap.xml are generated for you, and the SEO analyser scores 25 checks and tells you what to fix.
Editable after publishing
Change text, images and colours on the live page with the visual editor, on any plan. Pro adds a full in-browser code editor.
Private when you need it
Password-protect the whole site on Pro, or put an email gate in front of it and collect the addresses.
Frequently asked questions
Do I have to use MCP?
No. Click Choose folder on the dashboard and pick your build output — no API key, no config file, no setup. MCP earns its keep once you're deploying often enough that leaving the editor becomes the slow part.
Windsurf caps how many tools an agent can see. Is that a problem?
Windsurf lets you enable individual tools rather than a whole server, so you can keep just the ones you use — deploy, update files, list projects — and leave the rest off. That keeps the dplooy server small inside your tool budget.
Can Cascade do more than deploy?
Yes. The same tool set creates projects, updates files on a live site, uploads images to your media library, creates form endpoints and booking pages, and configures the AI chatbot. It's the platform, not a deploy button.
Is my API key safe in mcp_config.json?
It's a plain file on your machine, so treat it like any other credential. It lives in your home directory rather than your repo, which keeps it out of commits by default. You can revoke a key from Settings → API Keys at any time.
Does this work in Cursor, Claude Code or VS Code?
Yes — any MCP-capable client uses the same server. Cursor takes the identical JSON block in mcp.json, Claude Code takes a one-line claude mcp add, and claude.ai and ChatGPT connect to the remote server over OAuth with nothing to install.
Is it free?
Yes, on the free plan: 3 hosted projects, free SSL and analytics. Free-plan sites are removed after 3 days. Plus and Pro sites stay up indefinitely, and Pro adds custom domains and password protection.
Can I connect a git repo instead?
Yes. Click Deploy from GitHub, pick the repo and branch, and turn on Deploy on every push. If the repo is framework source, we detect it from package.json and offer to commit a workflow that builds on GitHub and deploys the result here.
Other ways to get there
Hosting for the other AI builders
Same platform, same free plan. Whichever tool wrote the site, it ends up on an address you own.
Ship without leaving Cascade
Create a free account, paste one block into mcp_config.json, and ask it to deploy.