How to Publish a Website from Claude Without Leaving the Chat
You are inside Claude. You just described the page you need and Claude generated the HTML. Now the HTML is sitting in the chat window and you need to get it live on the internet without opening another browser tab, copying the code, navigating to a hosting tool, pasting, and publishing manually.
The HTMLPub MCP connector removes all of those steps. Here is the full workflow for how to publish a website from Claude in a single conversation.
What the MCP Connector Does
Model Context Protocol (MCP) is an open standard that lets AI tools connect to external services during a conversation. The HTMLPub MCP connector gives Claude the ability to publish pages directly to HTMLPub, which means you get a live URL back in the same chat window where you described the page.
Without the connector, the workflow is: generate HTML, copy it, open a browser, go to your hosting tool, paste the code, click Publish, get a URL. That is six steps and two context switches for something that should be one instruction. For anyone publishing pages regularly, cutting that to one step compounds quickly.
What You Need
- Claude Desktop (the desktop app, not claude.ai in the browser; MCP requires the desktop client)
- An HTMLPub account (the free tier works for initial setup)
- Your HTMLPub API key (find it in your HTMLPub account settings under API)
Step 1: Install the MCP Connector
Open Claude Desktop. Go to Settings, then Developer, then MCP Servers. Add the HTMLPub server configuration. The exact JSON block, including the server URL and authentication format, is in the HTMLPub MCP Connector Tutorial.
After adding the configuration, restart Claude Desktop. You should see a small hammer icon near the input area, which indicates tool integrations are active. Type "what tools do you have available?" and Claude should mention HTMLPub publishing.
Step 2: Write Your Prompt
The prompt structure that produces the best results:
- Describe what the page is for
- Specify who it is aimed at
- List the key content or sections to include
- End with "and publish it to HTMLPub"
Here is a copy-paste ready example:
Build a landing page for a freelance copywriting service. The audience is small business owners who need website copy. Include a headline that focuses on conversion, a short description of services (web pages, email sequences, and product descriptions), three social proof lines, and a contact CTA. Use a clean, professional design with dark text on a white background. Publish it to HTMLPub.
Claude will generate the HTML based on your description and then call the HTMLPub connector to deploy it. You will see the tool call appear in the conversation, followed by a confirmation and the live URL.
Step 3: What Claude Generates
From a well-written prompt, Claude typically produces complete HTML with inline CSS for styling, a responsive layout that works on mobile and desktop, the copy and structure you described, and a clean functional design without placeholder text.
The page is self-contained, which is important for HTMLPub: all styles and scripts are in the file, so nothing breaks when it is published as a standalone HTML page.
Step 4: Iterate Without Leaving the Conversation
If the page needs adjustments, describe them in the same conversation and ask Claude to update and republish. You do not start over. The context from the original prompt stays active, so Claude understands what the page is and what you want to change.
Common iteration requests that work well:
- "Change the headline to focus on speed instead of quality, and republish"
- "Make the background dark navy instead of white, and republish"
- "Add a FAQ section with three questions about turnaround time, and republish"
Each change is one line of instruction. Each produces an updated live page.
What You Can Build This Way
Single-page sites with clear structure work best: landing pages, event pages, portfolio pages, product announcements, waitlist pages, and simple microsites. Claude's HTML output is consistent for self-contained pages.
Multi-page sites require publishing each page separately and building navigation manually. Claude can handle this in sequence within a conversation, but there is no automatic site-wide navigation sync. Plan for that if your project has more than two or three pages.
Real Example
We published 15 landing pages in one hour using this exact workflow. Average time per page was two minutes and 42 seconds from prompt to live URL. The full account of how that went is in 15 Landing Pages in One Hour.
For a narrower example of publishing a single page from Claude Code specifically, How to Publish a Landing Page from Claude Code covers that workflow step by step.
What to Do Next
Setup takes under five minutes. The full Claude MCP Connector Tutorial walks through every configuration step with the exact JSON you need.
Once it is working, publish something small first: a simple one-page site to confirm the connection is live and the URL comes back correctly. From there, the workflow is just conversation.