How to publish HTML from Cursor as a client-ready link
To publish an HTML report from Cursor, connect Foliyo’s hosted MCP server, authenticate, and ask Cursor Agent to publish your reviewed file. Foliyo gives the deliverable an online address with your chosen design, sender and access settings, so the client does not need your repository or editor.
What this workflow is for
Use it for a finished report, proposal or project handoff that a client can read in a browser. Start with approved material and remove internal comments, secrets and unrelated files. A full application with a backend needs its own deployment workflow.
You need Cursor, a Foliyo account and permission to use external tools in your workspace. The example below targets the Cursor editor. Browser-hosted and organization-managed agents may have different setup controls.
1. Add Foliyo to Cursor’s MCP configuration
Use .cursor/mcp.json in the current project, or ~/.cursor/mcp.json for your user configuration. Merge this entry with any existing mcpServers entries instead of replacing other tools. The URL points to Foliyo’s online service.
{
"mcpServers": {
"foliyo": { "url": "https://foliyo.io/mcp" }
}
}3. Turn the approved file into a deliverable
Name the exact file to use. Explain the recipient’s task and which sources are approved. Ask for a short, readable result with supporting evidence and a clear next action.
The following example uses fictional Northwind project material. Replace the file and client details with your own. Numbered choices should resolve missing details before the agent builds the page.
Create a Foliyo from the approved report.html in this project for Northwind. Preserve the findings, sources, limitations and next actions. Use a scrolling page with our approved client design guide and my consultancy as sender. Use a PIN and one shared link. Ask missing questions with numbered choices, then show the summary before building. Preflight the prepared HTML and inspect it before publishing. Return the online link. Do not publish source code, secrets or other project files, and do not email anyone.4. Inspect the prepared page before sharing
Ask the agent to inspect the output prepared by Foliyo rather than assuming the original HTML and published result are identical. Check supported content and publishing-mode requirements before relying on custom scripts or forms. A preflight result does not replace opening the page in a browser.
- Read beyond the first screen and confirm every expected section is present.
- Test the important navigation, images and source links at desktop and phone widths.
- Open the published URL as a recipient and verify the chosen gate.
- Confirm the output is a hosted link, not localhost or a file on your machine.
5. Revise without sending another URL
Tell Cursor to find and update the existing Foliyo. Include the precise change and check the access settings again. An authorized client connected to the same workspace can continue the work, subject to its permissions.
Find the Northwind report Foliyo and update the next-actions section from the approved changes below. Keep the existing URL and access settings. Show me the changes before publishing. Do not create a second Foliyo or send email.Common Cursor publishing problems
If Foliyo is missing, check the configuration file location, JSON syntax and whether the server is enabled in the current workspace. Review Cursor’s MCP controls for an authentication request or error.
If the browser callback fails, restart login from Cursor on the same computer. Do not forward or bookmark the callback URL. If updates to a page created in another tool are denied, check that you connected the same Foliyo workspace with the required workspace access.
If Cursor writes a local HTML file and stops, explicitly ask it to publish through the Foliyo MCP tools. If it cannot access those tools, resolve the connection rather than treating the local preview as a successful publication.
Sources and what has been verified
The configuration locations and remote-server setup were checked against Cursor’s documentation on 15 October 2026. This is a documentation-verified editor walkthrough, not a claim that every current Cursor account or version has passed a live end-to-end test. Always confirm the tool connection and recipient view in your own workflow.
Product guidance from Foliyo. See current plans and limits, connection instructions and our privacy policy. Send corrections or questions to hello@foliyo.io.