Create a website with Claude and publish it with Pagelet's MCP

Claude is great at writing websites. Pagelet is great at hosting them. With the Pagelet MCP server you can connect the two, so Claude builds the page and puts it online at a live pagelet.host URL without you ever opening a terminal or dragging a file anywhere.

In this guide we'll set up the connection (it takes about 30 seconds and there's no API key to copy) and then walk through a real use case: a wedding page with the schedule, travel tips and an RSVP form, built, published and updated entirely from a chat with Claude.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants use external tools. Pagelet's MCP server gives Claude these tools:

Once Claude has these tools, publishing a website is just a sentence: "Publish this page on Pagelet with the slug ana-and-leo."

Step 1: Connect Claude to Pagelet

There's no API key to create or copy. You add Pagelet's server URL, sign in with Google and click Allow.

Claude (claude.ai, Desktop and mobile):

1. Open Settings → Connectors and click Add custom connector.
2. Name it Pagelet, paste https://pagelet.host/mcp as the URL and click Add. Leave the advanced OAuth fields empty.
3. Click Connect, sign in with Google and click Allow access.

If you don't have a Pagelet account yet, signing in creates one.

Claude Code: one command, then sign in:

claude mcp add --transport http pagelet https://pagelet.host/mcp

Run /mcp inside Claude Code, pick pagelet → Authenticate and approve in the browser. Add --scope user to use it in every project.

The same URL works in ChatGPT, Cursor, VS Code and any other MCP client that supports sign-in; the setup page has the steps for each. Only scripts and clients that can't sign in need an API key, which you can create in your dashboard under API keys.

Step 2: Turn it on in a chat

Start a new chat, open the tools menu and make sure Pagelet is enabled. That's it: Claude can now publish to your account. Publishing counts against your plan: the free plan allows 10 sites of up to 5 MB each, and Pro (€2.99/month) lifts the site cap, raises the limit to 50 MB and adds custom domains.

Step 3: Describe the website

Now for the fun part. Here's the prompt for our use case, a wedding page:

Build a complete single-file HTML website (CSS and JavaScript inline) for our wedding.
Details: Ana & Leo, getting married on Saturday June 13, 2027 at Finca Son Bosch, Mallorca.
Include:
- A hero with our names, the date and a countdown to the big day
- The day's schedule (ceremony 16:00, aperitivo 17:30, dinner 20:00, party until late)
- Travel tips: nearest airport PMI, recommended hotels, taxi info
- An RSVP form (names, number of guests, dietary requirements) that shows a friendly
  confirmation message on submit and builds a mailto: link to [email protected]
Style: warm and elegant, cream and terracotta palette, serif headings, responsive
for phones. No external files except Google Fonts.

Claude writes the whole thing as one self-contained HTML file, ready to go online.

Step 4: Publish from the chat

No saving files, no uploading. Just say:

Publish this on Pagelet with the slug ana-and-leo

Moments later Claude replies with the link: your page is live at ana-and-leo.pagelet.host. Share the URL, or grab the QR code from your dashboard for the paper invitations. You choose the address: slugs are 3 to 40 characters of lowercase letters, digits and hyphens. Every publish is security-screened automatically, same as browser uploads.

Step 5: Iterate, the real superpower

Wedding details change. Guests get added, the aperitivo moves, a second bus is hired. Instead of editing HTML by hand, you just keep chatting:

The ceremony moved to 16:30 and we added a kids' corner at 18:00.
Update the page and republish it at the same address.

Claude edits the page, removes the old version and republishes it under the same slug, so ana-and-leo.pagelet.host shows the new schedule and every invitation you already sent still works. (Publishing to a slug that's still taken would get a random suffix like ana-and-leo-x7k2p1, which is why the remove-and-republish dance matters.)

A few more prompts that work well at this stage:

• "Add a section with our gift registry link."
• "Make the countdown match the new date and darken the hero for better contrast."
• "The RSVP form should warn if the guest count is above 10."

Each change is one message away from being live.

Step 6: Keep an eye on things

Ask Claude "Which of my Pagelet sites get the most views?" and it shows you every site with its URL, status, size and view count. You can also ask for details about one site or clean up old experiments. Everything is also visible in your dashboard.

Bonus: put it on your own domain

On Pro, Claude can connect a domain you own too:

Connect www.anayleo.com to the ana-and-leo site

Claude replies with two DNS records to add at your domain provider: a CNAME pointing to domains.pagelet.host and a TXT record that proves the domain is yours. Copy the TXT value in full, including pagelet-verify=. Once they're added, say "Verify the domain". Claude checks the records, tells you if anything is missing, and as soon as they're in place the page is live at https://www.anayleo.com with HTTPS set up automatically. DNS changes can take a few minutes to show up, so it's fine to ask again a bit later.

Good to know

• You stay in control. Claude can only touch sites in your own account, and you can disconnect it anytime from Dashboard → API keys & apps.
• Rate limits are generous. 100 publishes per hour and 1,000 MCP requests per hour, far more than any iteration session needs.
• Content is screened. Every publish passes security heuristics and an AI spam analysis; malicious content is blocked and quarantined automatically.
• It's not just weddings. Landing pages, portfolios, CVs, calculators, event pages, documentation: any complete HTML document works.

FAQ