If your website is already open in Cursor, publication can become part of the same agent workflow you use to edit the project.
Cursor supports remote MCP servers, including Streamable HTTP and OAuth. Once Deplion is connected, the agent can work with the project files and the publishing tools in the same session.
The short version: connect Deplion in Cursor, finish the site, then ask the agent to publish the current project and return the public URL.
Before you start
You need:
- a static website or landing page open in Cursor;
- a Deplion account;
- Deplion added as an MCP server in Cursor.
The workflow is best suited to frontend projects made from HTML, CSS, JavaScript, images, and other browser assets.
Step 1: Add Deplion to Cursor
Cursor lets you manage MCP servers from its customization settings or through mcp.json.
For a project-specific setup, use .cursor/mcp.json. For a connection you want available across projects, use your global Cursor MCP configuration.
A remote MCP entry follows this general shape:
{
"mcpServers": {
"deplion": {
"url": "YOUR_DEPLION_MCP_URL"
}
}
}
Use the endpoint and authentication details provided by Deplion. Cursor supports OAuth for remote MCP servers, so complete the sign-in flow if prompted.
Then check Cursor's available MCP tools and make sure Deplion is enabled.
Step 2: Finish the project in Cursor
Use Cursor normally until the page is ready.
For example:
Review this landing page for desktop and mobile. Fix obvious layout issues, but do not redesign it.
Then inspect the result yourself.
The point is to publish the version you actually want people to see, not an unfinished intermediate state.
Step 3: Ask Cursor to publish it
When the project is ready, ask:
Publish the current website with Deplion and give me the public URL.
Cursor already understands the current workspace. Deplion gives the agent the actions required to publish it.
After the agent finishes, open the returned URL in a browser and compare it with the version you reviewed in Cursor.
Step 4: Connect the existing contact form
If the 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 typical form can collect fields such as name, email, phone, company, service, and message.
The important part is that the form stops being decorative and starts producing leads.
Step 5: Test a real submission
Open the public site and submit the form yourself.
Use an obvious test value so it is easy to recognize later.
Then return to Cursor and ask:
Show me the latest lead from this project.
If the test lead appears, the page, form, and lead flow are working together.
Step 6: Publish later edits from the same workspace
Suppose you change the pricing section tomorrow:
Update the Start plan price and simplify the copy below it.
Review the result, then ask:
Publish the updated version with Deplion.
This works for content changes, images, sections, mobile fixes, calls to action, or any other frontend edit.
What if Cursor changes too much?
Agents sometimes rewrite more than you intended.
If the new public version is worse than the one before it, ask:
Roll back the project to the previous published version.
That gives you a clean recovery path without trying to manually reconstruct the previous page.
A prompt worth saving
Publish the current website with Deplion. Preserve the existing design. Make the contact form collect leads, verify that all required assets are included, check desktop and mobile, publish the finished version, and give me the public URL.
Common problems
Deplion tools do not appear in Cursor
Open Cursor's MCP settings and confirm that the Deplion server is enabled and authenticated.
If you configured it in mcp.json, verify that the URL is correct and that Cursor loaded the intended project or global configuration.
Cursor asks for tool approval
Cursor can ask for approval before running MCP tools. Review the action and approve it if it matches your publishing request.
The published page is missing styles or images
Ask:
Compare the public site with the current workspace. Fix missing styles, scripts, images, or other assets without redesigning anything, then publish the corrected version.
The form does not produce a lead
Ask Cursor to verify the Deplion form connection and republish, then submit another test yourself.
Do I need a repository on GitHub?
No. Cursor can work directly with the local project that is already open in the editor.
GitHub is still useful for source control and collaboration, but it is not required as an intermediate step between Cursor and Deplion.
Key takeaways
- Cursor supports remote MCP servers and can work with Deplion from the same project workspace.
- You can ask the agent to publish the current website instead of moving files through another workflow.
- A Deplion-connected form turns the page into a source of real leads.
- You can retrieve recent leads through the agent.
- Future edits can be published with another prompt.
- Published versions give you a rollback path.
The practical goal is simple: keep building in Cursor, but let the same agent take the finished project all the way to a public website that can receive inquiries.