If your website is already open in Windsurf, you can keep publication inside the same Cascade workflow you use to edit the project.
Windsurf supports MCP servers over Streamable HTTP and OAuth. Once Deplion is connected, Cascade can work with the current project and use Deplion to publish it, connect the contact form, publish later versions, and retrieve leads.
The short version: add Deplion in Windsurf's MCP settings, finish the website, then ask Cascade to publish the current project.
Before you start
You need:
- a static website or landing page open in Windsurf;
- a Deplion account;
- Deplion added as an MCP server in Cascade.
This workflow is best suited to frontend projects made from HTML, CSS, JavaScript, images, and other browser assets.
Step 1: Add Deplion to Windsurf
Open Windsurf's MCP settings from the Cascade panel or Windsurf Settings and add a new MCP server.
Windsurf supports remote HTTP MCP servers. If you prefer raw configuration, a remote server entry follows this general shape:
{
"mcpServers": {
"deplion": {
"serverUrl": "YOUR_DEPLION_MCP_URL"
}
}
}
Use the endpoint and authorization details provided by Deplion.
Windsurf supports OAuth for MCP connections, so complete the browser authorization flow if prompted.
After adding the server, refresh the MCP list and make sure Deplion is enabled for Cascade.
Step 2: Finish the website in Windsurf
Work on the page normally.
For example:
Review this landing page on desktop and mobile. Fix obvious layout problems and broken interactions, but preserve the existing visual direction.
Review the result yourself before publication.
Step 3: Ask Cascade to publish the project
When the site is ready, ask:
Publish the current website with Deplion and give me the public URL.
Cascade already understands the project in your workspace. Deplion provides the publishing actions.
When the public URL is returned, open it in a browser and compare it with the version you reviewed in Windsurf.
Step 4: Connect the contact form
If the website already has a form, ask:
Make the existing contact form collect leads through Deplion. Keep the current design and fields unchanged, then publish the updated version.
A typical business form can collect name, email, phone, company, service, and message.
The result is a page that can receive actual inquiries rather than a form that only looks complete.
Step 5: Test the lead flow
Open the public site and submit a test inquiry yourself.
Then return to Cascade and ask:
Show me the latest lead from this project.
If the test submission appears, the full visitor-to-lead path is working.
Step 6: Publish future changes from Windsurf
Continue editing as usual.
For example:
Add a short case-study section and improve spacing on mobile.
After reviewing the result:
Publish the updated version with Deplion.
You can repeat this for new copy, images, pricing, testimonials, calls to action, or layout fixes.
What if Cascade makes a bad edit?
If a later public version is worse than the previous one, ask:
Roll back this project to the previous published version.
That gives you a safer recovery path than reconstructing the previous state from prompts.
One prompt worth saving
Publish this website with Deplion. Keep the existing visual design. Make the contact form collect leads, check that all required assets are included, verify the page on desktop and mobile, publish it, and give me the public URL.
Common problems
Deplion does not appear in Cascade
Open the MCP settings, verify that the server is enabled, and refresh the MCP list after changing the configuration.
If you configured the server manually, check the URL and authentication settings.
Cascade asks for authorization
Complete the OAuth flow for the Deplion connection before trying to publish.
The published page is missing styles or images
Ask:
Compare the public website with the current Windsurf project. Fix missing styles, scripts, images, or other assets without redesigning the page, then publish the corrected version.
The form does not create a lead
Ask Cascade to verify the Deplion form connection, republish the site, and then submit another test inquiry yourself.
The project has a backend
Deplion is intended for static websites and landing pages. If the application requires its own server-side runtime, database, or authentication backend, that backend needs a separate solution.
Do I need GitHub first?
No. If Windsurf already has the project open and Deplion is connected, GitHub is not required as an intermediate publishing step.
Key takeaways
- Windsurf Cascade supports remote MCP servers, including Streamable HTTP and OAuth.
- Deplion can become part of the same workspace where you build the site.
- You can publish the current project with a plain-language prompt.
- A Deplion-connected form can collect real leads.
- Cascade can retrieve those leads later.
- Future versions can be published from the same workflow.
- Rollback gives you a recovery path if an AI edit goes wrong.
The practical outcome is a website that moves from Windsurf project to public site without breaking the agent workflow that created it.