Give your agent
a safe way to publish.
Connect once, add the publishing workflow, and ask in plain language. No repository, deployment setup, account, or API key is required for Free publishing.
Last updated
From agent to live page in three steps
https://html2web.iill.dev/mcpConnect your agent
Choose the app you already use. Cursor and VS Code open the reviewed connection inside the app; terminal clients use one copyable command.
Connect in Codex
Paste this in a terminal, then restart the current Codex session if the tools do not appear immediately.
codex mcp add html2web --url https://html2web.iill.dev/mcpConnect in Claude Code
Paste this in a terminal. The user scope makes HTML2WEB available in every project.
claude mcp add --transport http --scope user html2web https://html2web.iill.dev/mcpConnect in Cursor
Open Cursor, review the html2web remote server, then approve it. No local server package is installed.
Open in CursorCursor did not open? Copy the global config
Add this to ~/.cursor/mcp.json.
{
"mcpServers": {
"html2web": {
"url": "https://html2web.iill.dev/mcp"
}
}
}Connect in VS Code
Open VS Code, review the HTTP server configuration, and confirm the trust prompt.
Open in VS CodeVS Code did not open? Copy the user config
Run MCP: Open User Configuration, then add this server.
{
"servers": {
"html2web": {
"type": "http",
"url": "https://html2web.iill.dev/mcp"
}
}
}Install the Agent Skill
Install the workflow globally once. It teaches compatible agents to inspect content, choose the right expiry, verify the public page, and keep private management credentials out of chat.
Publishes and manages the link.
Guides safe, consistent tool use.
npx skills add https://html2web.iill.dev --skill publish-html2web --global --yesOnly want it in the current project?
npx skills add https://html2web.iill.dev --skill publish-html2web --yesThe skill is readable before installation. Review the official SKILL.md →
Publish your first page
Attach or point to an HTML or Markdown file, then send this prompt. It also acts as the connection check: a successful response includes a working public URL.
Publish this HTML for 1 hour, verify the page, and keep management credentials private.
Done looks like: public URL, expiry time, password status, and a verified page. Private ownership keys stay out of ordinary chat.
Available tools
- publish_html
- Publish an HTML string and return a share URL.
- publish_markdown
- Render and publish a Markdown string.
- publish_html_file
- Publish base64-encoded HTML or Markdown content.
- update_share
- Replace content using the manage token.
- delete_share
- Delete the share immediately.
- set_password
- Add, change, or remove viewer protection.
- set_expiry
- Change the expiry within the current plan.
- get_share_status
- Read status without retrieving page content.
Free limits
Up to 1 MB per file with 30-minute, one-hour, or 24-hour expiry. Fair-use publishing limits protect the public endpoint.
When the free quota is reached, the tool returns the reset time and a browser checkout link instead of a vague network error.
Reconnect with Pro OAuth
Pro uses a separate protected endpoint. Your MCP client handles OAuth; you never create, copy, or paste an API key.
https://html2web.iill.dev/mcp/pro- Open the HTTPS upgrade URL returned with the Free quota error.
- Sign in with Google or GitHub, then complete checkout in the browser.
- Wait until the verified subscription is active on your HTML2WEB account.
- Add or reconnect the Pro endpoint above and finish the browser authorization prompt.
Publishing receives Pro quota only after the subscription webhook is verified and the MCP connection is authorized for that account.
If your client cannot open upgrade links
Copy the upgradeUrl from the tool result into a normal browser. Complete sign-in and checkout there, then add the Pro endpoint as a new Streamable HTTP connection. If the client still uses the public Free endpoint, remove that stale connection and reconnect—do not paste a bearer token or checkout URL into the MCP configuration.
Manage tokens are ownership keys
A publish call returns a manage token for later changes. It is not an API key, is never needed to view the page, and should not be pasted into public channels.
Inspect source for passwords, API keys, personal data, or tokens before publishing. The viewer is isolated, but the shared page is reachable by anyone who has its URL unless you set a password.