Can Claude Code deploy to PreviewShip directly?

Yes, when PreviewShip MCP is configured. Claude Code can call the deploy tool and return the preview URL.

Does this only work for Claude?

No. The same workflow applies to Cursor, Windsurf, Codex, ChatGPT-generated files, and other tools that produce static HTML.

Can I upload Claude’s source project zip directly?

Only if it is already a static output folder. For framework source projects, build first and deploy the generated dist/build/out folder.

Should I use MCP or CLI?

Use MCP when the agent should own the deploy step. Use CLI when you want a transparent terminal command or CI-friendly fallback.

Guide / Claude HTML

Share Claude HTML artifacts without a full hosting setup

Turn HTML produced by Claude, Claude Code, or another coding agent into a browser-ready preview URL for teammates, clients, or stakeholders.

Updated 2026-05-11

Answer First

Claude can generate useful HTML, but the artifact still needs a public URL for review. With PreviewShip, deploy the generated .html file directly through MCP or CLI, or publish it from the web console by upload or paste, then share the returned preview link.

Key takeaways

Claude HTML artifacts become more useful when they can be reviewed as live pages.
MCP is the best path when Claude Code should complete deployment inside the workflow.
CLI remains a simple fallback for terminal-driven publishing.

Recommended workflow

Have Claude generate or update the HTML artifact.
Save the artifact as an .html file, or keep it as index.html with any referenced assets.
Use PreviewShip MCP or `npx previewship deploy ./report.html --json`.
Ask Claude to include the preview URL in its final response.

Why screenshots are not enough

Screenshots flatten the artifact and hide interactions, responsive behavior, and browser-specific rendering. A preview URL keeps the review closer to the real output.

Where MCP helps Claude workflows

MCP lets the agent call a deploy tool instead of merely suggesting a command. That makes the workflow feel complete: generate the page, deploy the artifact, and return the link.

If Claude creates a full app instead of one HTML file, ask it to build the app and deploy the output folder. If it creates one .html artifact, deploy that file directly.

FAQ

Can Claude Code deploy to PreviewShip directly?: Yes, when PreviewShip MCP is configured. Claude Code can call the deploy tool and return the preview URL.
Does this only work for Claude?: No. The same workflow applies to Cursor, Windsurf, Codex, ChatGPT-generated files, and other tools that produce static HTML.
Can I upload Claude’s source project zip directly?: Only if it is already a static output folder. For framework source projects, build first and deploy the generated dist/build/out folder.
Should I use MCP or CLI?: Use MCP when the agent should own the deploy step. Use CLI when you want a transparent terminal command or CI-friendly fallback.