Ship your Claude Artifact to a real URL

Anything Claude builds as a single HTML page can live at your-name.myminiapp.dev in a few minutes. Pick the route that matches where you are, then follow the numbers.

The no-tools route. Connect once, then publish by asking Claude in plain words. Works in the browser and the desktop app.

Add the connector. In Claude.ai open Settings → Connectors → Add custom connector. Name it My Mini App Hoster and paste this URL:
```
https://myminiapp.dev/mcp
```
You only do this once per Claude account.
Click Connect and sign in with Google. A Google window opens; choose the account you want your sites tied to. That Google account is your hosting account, so there is nothing else to register.
Open the chat with your artifact, or build one now. Any single-page artifact works: a game, a calculator, a dashboard, an interactive explainer.
Ask Claude to publish it, naming the site. For example:
```
Publish this artifact to myminiapp.dev as pocket-timer
```
Names are 1 to 63 lowercase letters, digits or hyphens, and become the subdomain. Claude sends the page's HTML for you; you do not copy anything.
Open the link Claude gives back. Your page is live at https://pocket-timer.myminiapp.dev over HTTPS on Cloudflare's network, straight away. Free sites carry a small ad strip and a "hosted on" badge; Premium sites carry neither.
Change it later by asking again with the same name. Every publish is a new deployment, and the old ones stay available in the dashboard for one-click rollback.

For the terminal. Same connector, added with one command. Best when the site is more than one file.

Register the server with Claude Code.

claude mcp add --transport http myminiapp https://myminiapp.dev/mcp

Authenticate. Inside Claude Code run /mcp, pick myminiapp, choose Authenticate, and sign in with Google in the browser tab that opens.
Ask Claude Code to publish. Point it at a folder or a file:
```
Publish ./dist to myminiapp.dev as pocket-timer
```
A folder goes up with all its files (the site needs index.html at the top level). A single HTML file is published as the whole site.
Use the other tools as you need them. The connector also lists your sites, shows a site's deployments, rolls back to an earlier one, and deletes a site. Ask for any of these in plain words.

No connector, just a browser. Download the artifact, zip it, upload it.

Save the artifact as a file. In Claude, open the artifact and use its download option. Rename the file to index.html.
Zip it with the file at the top level. Select the file itself, not a folder around it.
```
zip site.zip index.html
```
On Windows, right-click index.html → Send to → Compressed folder. On a Mac, right-click → Compress. Extra files like style.css or images can go in the same zip.
Sign in at myminiapp.dev/dashboard with Google.
Create the site. Under Sites, type a name and click Create site. The name becomes your subdomain.
Upload the zip. Click Upload zip on the new site's card. Validation runs first; if anything is wrong you get a plain list of what to fix. On success the card shows the live link and a preview.

For build pipelines and cron jobs. One token, one HTTPS call.

Create a token. In the dashboard under API tokens, name one and click create. The token is shown once; store it as a secret.

Post a zip to the deploy endpoint. The site is claimed automatically if the name is new.

zip -r site.zip index.html
curl -X POST https://myminiapp.dev/api/sites/pocket-timer/deploy \
  -H "Authorization: Bearer mah_..." \
  -H "Content-Type: application/zip" \
  --data-binary @site.zip

Read the response. It returns the deployment id, the public URL, and any warnings such as nearing your size limit. Errors come back as JSON with an error field and, for validation, an errors list.

The full endpoint list, including rollback, analytics and gallery listing, is at myminiapp.dev/docs.

Before you publish: what a site must look like

The checks are the same on every route. A site that passes them goes live immediately.

Entry file

index.html at the top level

Free plan

1 MB per site, 3 sites, 200 files, 2 MB upload

Premium plan

5 MB per site, 25 sites, 1,000 files, 10 MB upload

Scripts may be inline or loaded from well-known CDNs only: cdnjs, jsDelivr, unpkg, esm.sh, Tailwind, jQuery, Google Fonts and Google's ajax CDN. Claude Artifacts already follow this rule, so they pass as-is.
Files can be HTML, CSS, JS, JSON, text, images, fonts, PDFs and small audio. Video and archives are not accepted; this is app hosting, not media hosting.
Content that asks for passwords on someone else's behalf, hides a redirect, or collects card details is rejected at upload. The full list is in the acceptable use rules.

After it is live

Share the link. It is a normal HTTPS URL that works everywhere, including inside an iframe.
Roll back from the site's card in the dashboard. Each deployment is kept.
List it in the gallery. Give it a title and a line of description in the dashboard, and visitors can rate and favourite it.
Watch traffic. Views and unique visitors for the last 7 days on the free plan, 90 days with breakdowns on Premium.
Keep it alive. A site nobody visits for 75 days gets a warning, goes offline at 90, and is deleted at 120. One visit, or one new deploy, resets the clock.
Premium ($3.99 a month) removes the ads and badge, raises the limits, and adds password-protected sites and your own domain name.

If something goes wrong

index.html not found at the top level: The zip contains a folder. Re-zip the files themselves, not the folder that holds them.
script host "…" is not on the allowed CDN list: Move that script to cdnjs or jsDelivr, or paste its code inline. Anything else loads from unpkg or esm.sh too.
site exceeds 1 MB: Images are almost always the reason. Convert them to WebP, shrink them, or move to Premium for 5 MB.
slug is taken or reserved: Someone else has that name, or it is a system word like www or api. Pick another.
Claude says it cannot reach the connector: Open myminiapp.dev/status. If everything is Operational, remove and re-add the connector; the sign-in may have lapsed.

Still stuck? The dashboard's assistant can see your sites and their deployments. Ask it what happened.