DeepSeek Harness is built around composable plugins, including an MCP client plugin that can connect the agent to external tool servers.
That makes Deplion a natural addition when the result of an agent task is a static website or landing page that needs to become public.
The short version: add Deplion as a Streamable HTTP MCP server in DeepSeek Harness, make sure the agent can see the tools, then ask it to publish the current website.
Before you start
You need:
- DeepSeek Harness running;
- a website project available to the agent;
- a Deplion account;
- the DeepSeek Harness MCP client plugin configured for Deplion.
DeepSeek Harness is currently in developer preview and may introduce breaking changes, so verify the current configuration format if your installed version differs from this guide.
Step 1: Connect Deplion through the MCP client plugin
DeepSeek Harness includes an MCP client bridge that supports Streamable HTTP servers.
A Deplion entry in cordis.yml follows this general pattern:
- id: mcp-deplion
name: '@deepseek-ai/dsh-mcp-client'
config:
serverName: deplion
transport: streamable-http
url: YOUR_DEPLION_MCP_URL
Add the authentication details required by your Deplion connection.
Once loaded, DeepSeek Harness discovers the available MCP tools and exposes them to the model as normal agent tools.
You do not need to call those internal tool names yourself. Ask the agent for the outcome you want.
Step 2: Finish the website
Let the agent build or refine the website normally.
For example:
Review this landing page for desktop and mobile, fix obvious visual problems, and keep the current design direction.
Review the result before publication.
Step 3: Ask DeepSeek Harness to publish the project
When the website is ready, ask:
Publish the current website with Deplion and give me the public URL.
The agent has the project context, while the Deplion MCP connection gives it the publishing actions.
When the public URL is returned, open it yourself and compare it with the version you reviewed.
Step 4: Connect the contact form
If your website contains a contact form, ask:
Make the existing contact form collect leads through Deplion. Preserve the current design and fields, then publish the updated version.
A useful form might collect name, email, phone, company, service, or project details.
This turns the generated page into a working acquisition surface rather than leaving the form as a visual placeholder.
Step 5: Test the complete flow
Open the public site and submit a test inquiry yourself.
Then ask the agent:
Show me the latest lead from this project.
If the test submission appears, the site and form are working together.
Step 6: Publish future changes
Continue editing with DeepSeek Harness normally.
For example:
Rewrite the hero copy to be more concise and add one testimonial below the services section.
After reviewing the result:
Publish the updated version with Deplion.
The same workflow works for layout changes, pricing, copy, images, calls to action, and new sections.
If an agent edit goes wrong
If a later published version is worse than the previous one, ask:
Roll back this project to the previous published version.
That gives you a recovery path without reconstructing the earlier version from prompts.
One prompt worth saving
Publish this website with Deplion. Preserve 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
Deplion tools do not appear
Check that the MCP client plugin is loaded and that the Deplion server entry uses streamable-http with the correct endpoint.
Because DeepSeek Harness is in developer preview, also check whether your current release changed the plugin configuration.
Authentication fails
Verify the authorization settings for the Deplion MCP connection. The DeepSeek Harness MCP client supports custom headers for Streamable HTTP connections when required.
The public site is missing assets
Ask the agent to compare the public result with the current project, fix missing styles, scripts, images, or other assets, and publish again without redesigning the page.
The form does not create a lead
Ask the agent to verify the Deplion form connection, republish, and then submit another test yourself.
What kind of project works best?
Deplion is intended for static websites and landing pages. If your project requires its own server-side runtime, database, or authentication backend, that backend needs a separate solution.
Key takeaways
- DeepSeek Harness can consume Streamable HTTP MCP servers through its MCP client plugin.
- Deplion can give a DeepSeek Harness agent a direct publishing path for static websites.
- The agent can publish the project and return a public URL.
- A contact form can collect leads through Deplion.
- The same agent can retrieve those leads later.
- New versions can be published from the same workflow.
- Rollback provides a recovery path when an agent publishes an unwanted change.
The useful outcome is an agent that can take a website beyond generation and continue working with the published result after launch.