Input
HTML file, ZIP, or static folder
MCP HTML publishing · Updated September 18, 2026
Give Your AI Coding Agent a Publish Button
MCP HTML publishing is the new last mile for agent-generated pages: the model writes HTML, a tool call hosts it, and you get a URL. HTMLShare already gives Claude Code, Codex, and Cursor that loop through Skill, CLI, and API. It is not a hosted MCP server today.
What is MCP HTML publishing?
MCP HTML publishing lets an AI agent send generated HTML or static files to a hosting service and receive a shareable URL through a tool call. The category is forming around that contract, not around a single product name.
AI agent creates HTML → MCP / Skill / CLI calls a publish tool → hosting service returns a URL.
Action
Agent tool call or Skill/CLI publish
Output
Shareable browser URL
HTMLShare surface today
Skill, CLI, and Skill API — not a hosted MCP server
Independent hosts now sell the same workflow under MCP or agent-native labels: Stacktree, GitShare, drop, dochost, Share HTML, Just Publish, Bauta, HTMLvault, FolioDrop, and Shareable. HTMLShare matches the job with Skill and CLI. Searchers asking for an HTML hosting MCP server usually want files in, URL out, not a new application platform.
Publish HTML from Claude Code, Codex, or Cursor
Typical searchers already have the HTML. They want to stop downloading a file, opening a dashboard, uploading, and copying a URL. They want the agent to return the link.
Publish HTML from Claude Code
Claude Code MCP HTML · Claude Code publish HTML · Claude Code HTML hosting
Claude Code already writes reports, dashboards, and prototypes to disk. The missing piece is a publish tool. Install HTMLShare Skill, then ask Claude Code to publish the HTML. Recipients open a normal browser link and do not need a Claude account. If the Artifact tool is missing, this is the last-mile path.
Claude Code Artifact tool missingPublish HTML from Codex
Codex HTML hosting · Codex publish HTML · Codex MCP hosting
Codex can generate a static site or report in one run. HTMLShare Skill returns a preview URL in that same run. This is not Codex Sites and not a production deploy. It is a review link for browser-ready HTML, CSS, JavaScript, and assets.
Codex HTML previewPublish HTML from Cursor
Cursor MCP HTML · Cursor publish static site · Cursor generated page URL
Cursor can keep iterating a prototype in the editor. After Skill install, ask it to publish the page, then replace the same HTMLShare project on later revisions so the design-review URL does not churn.
Update HTML at the same URLnpx @htmlshare/cli install --agent all
One command installs the local Skill for Codex, Claude, and Cursor. After installing, use /htmlshare in any of them to publish the current HTML project.
MCP HTML publishing vs traditional deployment
Publishing an artifact is not the same as deploying an application. One-off reports, prototypes, interactive artifacts, and static mini-apps fit a lightweight publish. Production SaaS and backends fit a formal deployment.
JobPublishDeployWhy
One HTML report, dashboard, or prototype
Publish
Too heavy
There is no repo, build, or long-lived app to maintain.
Agent iterates v1 → v2 → v3 in one session
Replace the same URL
Preview-per-commit
Reviewers should keep one bookmark, not a new Vercel preview each revision.
Client or PM needs a browser link now
Files in, URL out
Git + project + env
The artifact is already finished HTML.
Production SaaS, auth, database, or CI
Wrong tool
Deploy
HTMLShare and MCP HTML hosts serve static files. They are not application platforms.
One HTML file vs ZIP static site
Use one file only when the page is genuinely self-contained. If the agent wrote CSS, JavaScript, images, fonts, or extra pages, keep the folder and publish it as a static project.
site/ ├── index.html ├── styles.css ├── script.js └── assets/
- Single HTML: Skill API /api/skill/publish, or upload one .html file.
- Multi-file project: /api/skill/publish-files, a ZIP, or a directory with index.html at the expected entry.
- Keep asset paths relative. Absolute local paths will break in the preview.
- HTMLShare publishes static files only. It does not run npm install, a server, or environment variables.
Keep the same URL while the agent iterates
Agents do not publish once. They revise. If every v2 creates a new URL, Slack, Notion, and client bookmarks go stale. Pro and Max users can replace an HTMLShare project and keep one URL; Free projects cannot be replaced.
Publish v1
Use a Pro or Max account through Skill or CLI to publish the first HTML or ZIP. Free projects and Guest one-hour previews cannot be replaced later.
Store the identity
Keep projectId, slug, or the preview URL with the agent run so the next session can find the same project.
Replace, do not fork
Pass replace or CLI --replace. Recipients refresh the original link. This is not a Git history or rollback UI.
See update HTML without changing the URL for the replace contract, limits, and what HTMLShare does not version.
Private agent-generated links
Some MCP HTML hosts sell password, expiry pickers, unlisted paths, and revoke tools. HTMLShare’s current privacy model is narrower. Write the boundary, then choose another host or production access control when you need a vault.
NeedHTMLShareNotes
Keep drafts out of Google
Yes
Preview responses are noindex. That is not a privacy boundary.
Unguessable review URL
Project URL
Share the link only with reviewers. Anyone who has it can open the live page.
Password, expiry picker, or revoke-from-agent
Not an agent tool today
Do not treat HTMLShare as a confidential vault. Delete the project in the dashboard when a link should stop working.
Plan retention
Yes
Guest previews last one hour. Free currently lasts 1 day, Pro 30 days, and Max is described as permanent. Replace refreshes expiry from the current plan.
For draft-versus-production search behavior, read private HTML hosting. Remove secrets before any agent publishes static files.
MCP vs CLI vs Agent Skill
MCP is a cross-client protocol. CLI is the terminal and CI path. An Agent Skill wraps the CLI/API so an existing coding agent can publish without a dashboard. HTMLShare ships the last two today.
SurfaceWhat it is forHTMLShare now
MCP server
Any MCP client can call the same tools after one connector add.
Not currently offered as a hosted HTMLShare MCP endpoint.
Agent Skill
Wraps an existing publish CLI/API so Claude Code, Codex, and Cursor can say publish this.
Current agent-native path. Install with npx @htmlshare/cli install --agent all.
CLI
Terminal, CI, and scripts. Useful when a human or job already has the files.
Same publisher the Skill runs, including --replace for Pro and Max projects.
Skill API
Programmatic publish from an agent runtime or internal tool.
POST /api/skill/publish for one HTML file; POST /api/skill/publish-files for a static project.
If you specifically need claude mcp add against a hosted MCP URL, that is a different product surface. If you need the agent to return a link, HTMLShare Skill already does that job.
FAQ
MCP HTML publishing questions
What is an MCP HTML publishing server?
It is a Model Context Protocol server that exposes publish tools to an AI client. The agent sends HTML or static files through a tool call and receives a shareable URL. HTMLShare currently provides that same files-in, URL-out loop through Skill, CLI, and the Skill API rather than a hosted MCP endpoint.
Can Claude Code publish HTML through MCP?
Yes, with any MCP HTML host that Claude Code can connect to. HTMLShare is not a hosted MCP server today. Install the HTMLShare Skill in Claude Code, then ask it to publish the generated HTML, ZIP, or static folder. The Skill returns a browser URL.
Can Codex publish a website through MCP?
Codex can publish static HTML through HTMLShare Skill or CLI. That is agent-native publishing, not a Codex Sites deployment and not an HTMLShare MCP connector. The result is a review URL for browser-ready files, not a production app with a build pipeline.
Can Cursor publish HTML through MCP?
Cursor can use MCP servers when they are configured. HTMLShare’s current Cursor path is the Skill: install it, then ask Cursor to publish the static page. Recipients open a normal HTTPS link and do not need Cursor.
How do I give an AI agent a share button?
Give it a publish tool. For HTMLShare, run npx @htmlshare/cli install --agent all, then tell Claude Code, Codex, or Cursor to publish the HTML. The agent uploads the files and returns the preview URL in the same run.
Can an MCP server return a public URL?
Yes. That is the category contract: files in, URL out. HTMLShare Skill and API responses include a project URL. HTMLShare preview links are noindex. Anyone with the URL can open a live preview.
Can I publish HTML without GitHub?
Yes. MCP HTML publishing, HTMLShare Skill, and HTMLShare CLI do not require a repository, GitHub Pages, or CI. Use Git when you want source history. Use a publish primitive when the agent already has a finished HTML artifact.
Can an AI agent upload a ZIP website?
Yes. HTMLShare accepts a self-contained HTML file or a static ZIP/folder with index.html plus relative CSS, JavaScript, images, fonts, and other assets. Guest uploads are 1 MB HTML and 3 MB ZIP. Signed-in projects accept 5 MB HTML and 20 MB total.
Is MCP hosting the same as deployment?
No. Publishing an artifact is not deploying an application. MCP HTML publishing is for a finished report, prototype, dashboard, or static mini-app. Vercel, Netlify, and Cloudflare Pages remain the fit when you need a repo, build, env vars, or a long-lived production site.
Can an agent update the same URL?
Yes, for a Pro or Max HTMLShare project. Pass replace with the previous project ID, slug, or preview URL on the Skill API or CLI --replace. Free projects cannot be replaced; Guest previews and ordinary browser uploads create a new project instead.
Have HTML from an agent already?
Install the Skill, say publish this, and send the URL. Keep replace for the next revision of the same page.