miinideckmiinideck
PricingUse casesBlog
Sign in
Use cases/Let Claude Code publish the page it just built as a private link, without leaving the terminal

Publish HTML straight from Claude Code — and keep the same link as it changes.

Claude Code just wrote you a report, a dashboard, a one-pager — and now it's a file on your disk that somebody else needs to see. The usual next steps are a deploy config you don't want, or a manual upload you'll forget to repeat. Connect miinideck as an MCP server once and the loop closes itself: Claude Code publishes the page to a private, unguessable link, and when you iterate it replaces the contents at that same link rather than minting a new one. The person you sent it to never gets a second URL.

Try it now

Drop a file — get a private link in seconds. No sign-up.

Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.

Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.

How it works

  1. 1

    Connect miinideck as an MCP server in Claude Code, once. It authenticates as you, so the tools can only reach pages on your own account — there's no anonymous key to hand around, and nothing to configure per project.

  2. 2

    Ask for the link in plain language: publish this, share this, get me a URL for this. Claude Code passes the finished HTML to the create tool and hands back an unguessable link that's no-indexed by default. Optionally it can set a password, an expiry, or file the page under one of your projects at the same time.

  3. 3

    Iterate. When you ask for a change, Claude Code replaces the contents of the page it already published — same link, password and expiry preserved, each replacement kept as a numbered version. One note worth knowing up front: HTML travels through the connector as text, so it fits pages under roughly 100 KB. For a bigger build, send the bytes with the CLI (npx miinideck deploy ./dist) or the web uploader instead — the link still stays the same.

Frequently asked questions

How do I publish a page from Claude Code without setting up hosting?

Connect miinideck as an MCP server and ask Claude Code to publish or share the file. It calls the create tool with the finished HTML and returns a private, unguessable link straight in the conversation. There's no deploy pipeline, no hosting account to configure per project, and no build step — the page is live the moment the tool returns.

Can Claude Code update a page it already published, instead of making a new link?

Yes, and that's the part worth setting up for. The update tool replaces the contents of a page you published earlier while keeping the same URL, and the password, expiry, and title stay as you set them. Each replacement is stored as a numbered version rather than overwriting history. This matters because it means you can send the link before the work is finished — whoever you sent it to keeps seeing the current version without you sending anything again.

Is there a size limit when publishing through the connector?

Yes, and it's worth knowing before you build a habit on it. The HTML travels as a text argument through MCP, which caps it around 100 KB in practice — comfortably enough for a single self-contained page, report, or dashboard. For a larger file or a multi-file build, don't push it through the connector; upload the bytes with the CLI (npx miinideck deploy ./dist) or the web uploader, neither of which has that limit. If the page already exists, the link is unchanged either way.

Does the connector have access to my whole account?

It acts as you, on your own pages only — publishing, listing what you've published, listing your projects, and replacing content on a page you own. It's authenticated rather than key-less by design: identity comes from your sign-in, not from a token pasted into a config file, so there's nothing to leak that would let someone else publish under your name.

Does this work with other AI tools, or only Claude Code?

Anything that speaks MCP can use it — Claude Code is just the most common place people hit this problem, because it produces finished files locally and then leaves you holding them. The same connector works from other MCP-capable clients. If your tool doesn't do MCP, the CLI and the web uploader get you to the same private link, you just trigger it yourself.

What does the person receiving the link have to do?

Open it. There's no account, no sign-in, and nothing to install — it's an ordinary web page in their browser, on any device. The link is unguessable and no-indexed, so it won't surface in search and only reaches the people you send it to. Add a password if the content needs one; free on every plan.

Learn more

  • Share a Cursor buildWhen the output is a build, not one file.
  • A link that never expiresWhat an iterating link needs underneath it.
  • Host an AI artifactThe same private link for anything AI builds.
  • PricingFree to start; never-expiring links on Solo.

More use cases

  • Revise a page you already sent someone without issuing a new URL
  • Get a stable private link for a bolt.new build
  • Host a built Slidev deck as a private link to send before a talk or a review round

Start free. Keep it private.

No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.

Get started free →Try without signing in
miinideck

HTML files, finally as links — for AI builders, agencies, and consultants. Default-noindex, default-private, default-yours.

Product

  • Pricing
  • Use cases
  • Try it free

Resources

  • Blog
  • Featured on
  • Report abuse

Legal

  • Privacy
  • Terms
© 2026 miinideckMade for people who don't want their work indexed.