Publish Websites with Claude Using MCP
To publish a web page from Claude, add HTMLPub’s MCP server (url: https://mcp.htmlpub.com/mcp) to your Claude config, authenticate once via OAuth, then ask Claude to build the page — it writes the HTML and publishes it to a live, shareable URL in seconds. Setup needs no API key and works on every plan including Free.
Building and previewing pages is free; publishing a page live requires a paid plan starting at $10/month. The same MCP server also works with Claude Code, Cursor, Windsurf, and any MCP-compatible client.
What is the Model Context Protocol?
The Model Context Protocol (MCP) is an open standard created by Anthropic that lets AI models interact with external tools and services. Think of it as a universal plug system for AI. Instead of copying and pasting between your AI conversation and different apps, MCP lets Claude reach out and use tools directly — reading data, creating content, and taking actions on your behalf.
Before MCP, if you wanted Claude to build you a web page, the workflow looked like this: ask Claude to write HTML, copy the response, open a hosting platform, paste the code, configure settings, and hit publish. With MCP, you say “build me a landing page” and Claude does everything in one step — writing the HTML and publishing it to a live URL automatically.
MCP is not specific to HTMLPub. It is an open protocol that any service can implement, and any MCP-compatible AI client can connect to. Anthropic designed it to be the standard way AI models interact with the outside world — similar to how USB standardized how devices connect to computers. HTMLPub was one of the first publishing platforms to implement a production MCP server, making it possible to go from conversation to live website without leaving your AI client.
How MCP works, in simple terms
- MCP Server — A service (like HTMLPub) exposes a set of tools that AI can use. HTMLPub’s server lives at mcp.htmlpub.com.
- MCP Client — An AI application (like Claude Desktop, Cursor, or Windsurf) that connects to MCP servers and makes tools available to the AI model.
- Tools — Specific actions the AI can take. HTMLPub provides tools like create_page, edit_page, and list_pages.
- Authentication — When Claude first uses an HTMLPub tool, you authenticate via OAuth. After that, Claude can publish on your behalf.
HTMLPub’s MCP Integration
HTMLPub’s MCP server gives Claude (and any MCP-compatible AI) the ability to create, read, edit, and manage web pages and sites. It is a full publishing toolkit accessible through natural conversation. Here is what Claude can do when connected to HTMLPub:
create_page
Create a new HTML page and publish it to a live URL instantly. Supports full HTML, CSS, and JavaScript.
edit_page
Update an existing page’s HTML content. Make changes to any page you own without republishing from scratch.
get_page
Retrieve the current HTML content and metadata of any page. Useful for reviewing what is live before making edits.
list_pages
List all pages in your account. See titles, slugs, URLs, and status at a glance.
analyze_url
Analyze any URL for design patterns, layout structure, and content. Great for “build something like this” prompts.
import_asset_from_url
Import images, fonts, or other assets from external URLs directly into your page’s asset library.
list_sites
View all multi-page sites in your account. Sites group related pages together under one project.
create_site
Create a new multi-page site project. Organize landing pages, marketing pages, and more under one roof.
Every tool works the same way: you describe what you want in natural language, and Claude translates your request into the right tool call with the right parameters. You never need to learn an API or write integration code — just talk to Claude.
Step-by-Step: Publish a Page with Claude
Here is exactly how to go from zero to a live web page using Claude and HTMLPub’s MCP integration. The entire process takes under two minutes.
1 Open your Claude Desktop config
In Claude Desktop, go to Settings → Developer → Edit Config. This opens your claude_desktop_config.json file. If you are using Claude Code, Cursor, or Windsurf, the config location varies — check your client’s MCP documentation.
2 Add the HTMLPub MCP server
Add the following to your config file. If you already have other MCP servers configured, add htmlpub alongside them in the mcpServers object:
{
"mcpServers": {
"htmlpub": {
"url": "https://mcp.htmlpub.com/mcp"
}
}
}
That is the entire configuration. HTMLPub uses the streamable HTTP transport, so there is no local binary to install, no Docker container to run, and no API keys to manage. The URL points directly to HTMLPub’s production MCP server.
3 Restart Claude Desktop
Close and reopen Claude Desktop (or your AI client). When it loads, you should see HTMLPub listed among your available MCP tools. In Claude Desktop, look for the tools icon in the chat input area — HTMLPub’s tools will appear there.
4 Authenticate
The first time Claude uses an HTMLPub tool, it will trigger an OAuth authentication flow. A browser window will open where you can sign in to your HTMLPub account (or create one). Once authenticated, Claude can build and publish pages to your account. Building and previewing is free; publishing live requires a paid plan.
5 Ask Claude to create a page
Now just tell Claude what you want. Be as specific or as vague as you like. Here are some examples:
// Simple request
Create a landing page for my SaaS product called "Beacon".
It’s a customer analytics platform. Use a dark theme with
purple accents. Include a hero section, three feature cards,
a pricing table with Free and Pro tiers, and a footer.
// Claude will generate the full HTML and call create_page
// automatically. You’ll get back a live URL in seconds.
Claude will generate the complete HTML, CSS, and JavaScript, then call HTMLPub’s create_page tool to publish it. You will see the tool call happen in real time, and Claude will share the live URL when it is done.
6 Review and iterate
Click the URL to see your live page. Then just keep talking to Claude to make changes:
- “Make the hero headline bigger and change the CTA button to green”
- “Add a testimonials section below the features”
- “Replace the pricing table with a simple ‘Contact Sales’ form”
- “Add meta tags and Open Graph data for SEO”
Each change is published instantly. Claude uses the edit_page tool to update your live page in place — no redeployment, no build step, no waiting.
Example Prompts for Claude
Not sure what to ask Claude to build? Here are real prompts that work great with HTMLPub’s MCP integration. Each one will result in a fully published, live web page.
Using HTMLPub MCP Programmatically
Claude Desktop is the most popular way to use MCP, but HTMLPub’s MCP server works with any MCP-compatible client. Here is how to connect it to the tools developers use every day.
Cursor
Cursor has built-in MCP support. Open Settings → MCP and add HTMLPub as a new server with the URL https://mcp.htmlpub.com/mcp. Once connected, you can ask Cursor’s AI to publish pages while you are coding. This is powerful for building marketing pages alongside your app — ask Cursor to create a landing page that matches your app’s design system, and it will publish it to HTMLPub without you switching tools.
Windsurf
Windsurf supports MCP servers through its configuration. Add HTMLPub to your MCP configuration following Windsurf’s documentation, using the same server URL. Windsurf’s Cascade AI can then create and manage HTMLPub pages as part of your development workflow.
Claude Code (CLI)
If you use Claude Code in the terminal, HTMLPub’s MCP server works there too. Add the server to your Claude Code MCP configuration:
// Add to your Claude Code MCP settings
{
"mcpServers": {
"htmlpub": {
"url": "https://mcp.htmlpub.com/mcp"
}
}
}
With Claude Code, you can script entire publishing workflows. Ask it to read a local markdown file and publish it as a styled HTML page, or generate a batch of landing pages from a spreadsheet of product data.
Automating page updates
Because MCP tools are just function calls under the hood, you can build automated workflows around them. Common patterns include:
- CI/CD publishing — Trigger Claude to update your HTMLPub pages when you push to your main branch
- Content pipelines — Feed Claude a list of topics and have it generate and publish a page for each one
- Design iteration — Use analyze_url to study a competitor’s page, then ask Claude to create a better version
- Bulk updates — Use list_pages to get all your pages, then ask Claude to update the footer or branding across every page
MCP vs Traditional Web Builders
Publishing with Claude + MCP is a fundamentally different workflow. Here is how it compares to traditional website builders.
| Dimension | Claude + HTMLPub MCP | Traditional Web Builders |
|---|---|---|
| Speed to publish | ✓ Seconds (one conversation) | Minutes to hours (manual setup) |
| Design iteration | ✓ Describe changes in words | Click, drag, adjust, preview, repeat |
| Code control | ✓ Full HTML/CSS/JS | Limited to builder’s component system |
| Learning curve | ✓ Zero — just describe what you want | Must learn each builder’s interface |
| Batch operations | ✓ Create/update many pages at once | ✗ One page at a time |
| SEO control | ✓ Full meta, OG, JSON-LD | Varies — often limited |
| Integration with dev tools | ✓ Cursor, Windsurf, Claude Code | ✗ Separate from your IDE |
| Visual editor | ✗ No drag-and-drop | ✓ Visual WYSIWYG editing |
| Predictability | AI output varies — may need iteration | ✓ What you see is what you get |
The MCP approach is not a replacement for visual builders — it is a different paradigm. If you know exactly how you want a page to look and prefer pixel-level control through a visual interface, a traditional builder may be the right choice. But if you want to move fast, iterate through conversation, and publish pages that are fully customizable at the code level, Claude + HTMLPub MCP is dramatically faster.
Common questions
How do I publish a web page from Claude using MCP?
Add HTMLPub’s MCP server to your Claude config (url: https://mcp.htmlpub.com/mcp), then authenticate once via OAuth (no API key needed). Then ask Claude to build a page — it generates the HTML, CSS, and JavaScript and calls the create_page tool to publish it to a live, shareable URL. Building and previewing is free; publishing a page live requires a paid plan starting at $10/month.
Is the HTMLPub MCP server free to use?
Yes. The MCP server is included on every plan, including the permanent Free plan, and connects via OAuth with no API key or credit card. On Free you can build and preview up to 5 pages with the full AI editor, but pages are not published live. Publishing a page live requires a paid plan starting at $10/month. There is no time-limited trial.
How fast is publishing a page with Claude and MCP?
Once connected, you go from a natural-language prompt to a published page in a single conversation — Claude returns a live, shareable URL in seconds. There is no build step, no deploy pipeline, and no redeployment when you ask Claude to make edits.
Can I use a custom domain for pages published via MCP?
Yes, on a paid plan. Starter ($10/month) includes 1 custom domain, Pro ($29/month) includes 1, and Business ($49/month) includes 2. You point a CNAME record and SSL is handled automatically. The Free plan does not include custom domains.
Which AI tools work with HTMLPub’s MCP server?
Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible client. The server URL is the same everywhere: https://mcp.htmlpub.com/mcp. Any tool that supports the Model Context Protocol can connect and use HTMLPub’s publishing tools.
Do I need to know how to code to publish from Claude?
No. Claude generates the HTML, CSS, and JavaScript from your natural-language description and publishes it for you via MCP. You describe what you want — a landing page, portfolio, or waitlist page — and Claude writes the code and publishes it automatically.
Publish your first page with Claude
Add one line to your Claude config and start building. Free to build and preview; publish live on a paid plan.