If Claude Code has already built your website, the next step does not have to be a separate manual workflow.
With Deplion connected through MCP, Claude Code can publish the current project, return a public URL, connect your existing contact form to lead collection, publish later updates, and roll back a version if an AI edit goes wrong.
The short version: connect Deplion to Claude Code once, open the website project in Claude Code, then ask Claude to publish it.
What you will have when you are done
By the end of this guide, you will have:
- a public URL for your Claude Code project;
- a working contact form that saves submissions as leads;
- the ability to ask Claude Code for recent leads;
- a simple way to publish later edits;
- version history for rollback.
This workflow is best suited to static websites and landing pages made from HTML, CSS, JavaScript, images, and other browser assets.
Step 1: Connect Deplion to Claude Code
Claude Code supports remote MCP servers over HTTP and OAuth authentication.
Add Deplion using the MCP connection details shown in your Deplion account or documentation. The Claude Code command follows this pattern:
claude mcp add --transport http deplion YOUR_DEPLION_MCP_URL
Then start Claude Code and run:
/mcp
If Deplion requires authorization, Claude Code will guide you through the browser sign-in flow.
You only need to configure the connection once for the scope you choose.
Step 2: Open the project you want to publish
Move into your website project and start Claude Code as usual:
cd my-website
claude
Before publishing, finish the version you want visitors to see.
For example:
Check this landing page on desktop and mobile. Fix obvious layout issues, but keep the current visual direction.
Then review the result locally.
Step 3: Ask Claude Code to publish it
When the project looks right, ask:
Publish the current website with Deplion and give me the public URL.
Claude Code already has access to the project files, while Deplion gives it the publishing tools it needs.
You do not need to move the project into a separate manual upload workflow just to make it public.
When the operation finishes, Claude Code can return the URL of the published site.
Open that URL yourself before sharing it.
Step 4: Make the contact form work
If the website already contains a contact form, ask Claude Code to connect it to Deplion while preserving the design:
Make the existing contact form collect leads through Deplion. Keep the current layout and styling unchanged, then publish the updated version.
A normal lead form might contain:
- name;
- email;
- phone;
- company;
- project details;
- message.
For a typical landing page, you do not need to create a separate application just to receive these submissions.
Step 5: Test the full visitor journey
Do not stop after checking that the page loads.
Open the published site and submit a test inquiry yourself.
For example:
Name: Test User
Email: [email protected]
Message: Testing the contact form before launch.
Then return to Claude Code and ask:
Show me the latest lead from this project.
If Claude returns the test submission, you have verified the complete path from visitor to lead.
Step 6: Publish future changes from the same project
The useful part of this workflow becomes clearer after the first publication.
Suppose you later ask Claude Code:
Replace the hero headline with “Launch your project faster” and make the mobile spacing slightly tighter.
After reviewing the change, simply say:
Publish the updated version.
You can repeat the same flow whenever you change copy, pricing, images, testimonials, calls to action, or layout.
What if Claude Code changes the wrong thing?
AI-assisted development is fast because an agent can modify many files for you. It also means an unwanted edit will eventually happen.
If the latest published version is worse than the previous one, ask:
Roll back this project to the previous published version.
That is usually safer than trying to reconstruct the old state from conversation history.
One prompt worth saving
For a finished landing page, this is a useful reusable prompt:
Publish this website with Deplion. Keep the existing design. Make the current contact form collect leads. Check that all required files and assets are included, verify the page on desktop and mobile, publish it, and give me the public URL.
After publication, test the form once yourself.
Common problems
Claude Code cannot see Deplion
Run /mcp and check whether the Deplion MCP connection is available and authenticated.
If it is missing, add the remote MCP connection again using the details from Deplion.
The page is public but looks different
Ask Claude Code:
Compare the published website with the current project. Fix missing styles, scripts, images, or other assets without redesigning the page, then publish the corrected version.
The form appears but submissions do not arrive
Ask:
Verify that the published contact form is connected to Deplion lead collection. Keep the existing design, fix the integration if needed, republish the site, and tell me when to test it again.
Then submit another test lead yourself.
The project needs its own backend
Deplion is intended for static websites and landing pages. If the project depends on a separate server-side runtime, database, authentication service, or custom backend application, that backend needs its own solution.
Do I need GitHub first?
No. GitHub can still be useful for source control, but it is not a required intermediate step in this workflow.
If Claude Code already has the project open and can use Deplion through MCP, you can ask it to publish the current website directly.
Can I use my own domain?
Yes. After the project is published and tested, you can connect a custom domain according to the options available on your Deplion plan.
A practical sequence is:
publish → test → connect domain → keep updating through Claude Code.
Key takeaways
- Claude Code can work with Deplion through MCP.
- You can publish the project from the same Claude Code session where you edit it.
- A contact form can collect leads without creating a separate form application.
- You can ask Claude Code to show recent leads later.
- New versions can be published with another prompt.
- If an AI edit goes wrong, you have a rollback path.
The useful end result is not a folder of generated files. It is a public website that can receive inquiries and remain manageable from the same AI workflow that created it.