If Gemini CLI has already helped you build a website, you can keep the publishing step inside the same terminal workflow.
Gemini CLI supports remote MCP servers over HTTP. Once Deplion is connected, Gemini can use the project files in your current workspace and publish the finished site without adding a separate manual upload process.
The short version: add Deplion as an MCP server, start Gemini CLI in your project, and ask Gemini to publish the current website.
Before you start
You need:
- Gemini CLI installed;
- a static website or landing page available in the current project directory;
- a Deplion account;
- Deplion configured as an MCP server.
This workflow is intended for static frontend projects made from HTML, CSS, JavaScript, images, and similar browser assets.
Step 1: Connect Deplion to Gemini CLI
Gemini CLI includes MCP server management from the command line.
For a remote HTTP server, the command follows this pattern:
gemini mcp add deplion YOUR_DEPLION_MCP_URL --transport http
Use the endpoint provided by Deplion.
If authorization is required, complete the MCP authentication flow. Inside Gemini CLI you can inspect configured servers with:
/mcp list
If Deplion does not appear correctly, reload MCP connections with:
/mcp reload
Once the server is connected, you do not need to call individual Deplion tools manually. Ask Gemini for the result you want in normal language.
Step 2: Start Gemini CLI in the project
Move into the project directory and start Gemini CLI:
cd my-website
gemini
Then ask Gemini to review the current version before publication:
Check this landing page for desktop and mobile. Fix obvious layout issues and broken interactions without changing the overall design.
Review the result yourself.
Step 3: Publish the website
When the site is ready, ask:
Publish the current website with Deplion and give me the public URL.
Gemini already has the project context, and the connected Deplion MCP gives it the actions required to publish the website.
When Gemini returns the URL, open it in a browser and compare it with the version you reviewed locally.
Step 4: Make the form collect leads
If the site already has a contact form, tell Gemini:
Make the existing contact form collect leads through Deplion. Preserve the current visual design and fields, then publish the updated version.
The form can collect information such as name, email, phone, company, service, and message.
For a normal landing page, you do not need to build a separate application just to receive those submissions.
Step 5: Test the full flow
Open the public site and send a test submission yourself.
Then ask Gemini CLI:
Show me the latest lead from this project.
If the test inquiry appears, the visitor-to-lead flow is working.
Step 6: Publish future edits
Continue working with Gemini CLI normally.
For example:
Add a short FAQ section below pricing and make sure it works well on mobile.
After reviewing the change:
Publish the updated version with Deplion.
The same workflow works for copy changes, image replacements, pricing updates, testimonials, and layout improvements.
What if Gemini makes the wrong change?
If an AI edit produces a worse public version, ask:
Roll back this project to the previous published version.
That gives you a reliable recovery path without reconstructing the previous page from prompts.
One prompt worth saving
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 desktop and mobile, publish it, and give me the public URL.
Common problems
Gemini CLI cannot see Deplion
Run /mcp list and check the connection status.
If needed, use /mcp reload after fixing the server configuration or authentication.
The published site is missing images or styles
Ask:
Compare the public website with the current project. Fix missing styles, scripts, images, or other assets without redesigning anything, then publish the corrected version.
The form does not create a lead
Ask Gemini to verify the Deplion form connection and republish. Then submit another test inquiry yourself.
The project needs server-side code
Deplion is designed for static websites and landing pages. If the application depends on a separate server-side runtime, database, or custom backend, that backend needs its own solution.
Do I need GitHub?
No. GitHub is useful for source control, but it is not required between Gemini CLI and Deplion when the agent already has access to the project files.
Key takeaways
- Gemini CLI supports remote HTTP MCP servers.
- Deplion can become part of the same terminal workflow you use to build the website.
- You can publish a finished project with a plain-language instruction.
- A Deplion-connected form can collect real leads.
- Gemini can access recent leads after publication.
- Later changes can be published with another prompt.
- Version history gives you a rollback path.
The goal is to move from “Gemini built the project” to “the website is public, the form works, and Gemini can keep maintaining it.”