How to share a Claude artifact with a client without making it public

You asked Claude for a pricing page, a prototype, or a walkthrough. It built the HTML in minutes. Now a client needs to open it, leave feedback, and come back after you change it. The client is outside your Claude org — they should not need a Claude seat or any AI tool. Feedback should happen on the live page, not in email. Docklet is built for that handoff: a universal link anyone can open, comments in place, and publish from any MCP-connected assistant.

When Claude Publish is the right choice

Claude Publish is a strong fit when the recipient already has Claude (a colleague on your Team plan), when you want a quick public demo with no review loop, or for a one-off share you will not revise. It is included in your Claude subscription and works well for those jobs.

Paste-and-host tools such as NudgeHost, PreviewShip, Static.app, and Netlify Drop are designed to turn HTML into a URL quickly — a complementary path when you need public hosting without a review workflow. For a deeper comparison, see Claude Publish vs Docklet and publish without Netlify Drop.

When a client is outside your Claude org

As of August 2026, Anthropic's documentation describes Claude Publish as scoped for demos and in-org sharing. On Free, Pro, and Max plans, Publish creates a public claude.ai link — anyone with the URL can open it, and comments are off on public pages. On Team and Enterprise, Publish is typically org-only: that default is built for company-internal sharing — viewers need Claude seats in your organization, public sharing is often disabled, and there is no per-email allowlist or custom domain. Anthropic's docs also note that unpublishing removes the link; a new publish uses a new URL.

When your recipient is a teammate on Claude Team and org sharing covers your workflow, Claude Publish may be all you need. When the recipient is a client outside your org, Docklet adds what that handoff needs: they open without your AI tool, comment on the page, and you publish from any MCP client — with email allowlist and the same URL when you ship v2.

What a client-ready link needs

Three things matter for a client outside your org:

1. Open without the tool — a normal browser URL; no Claude, ChatGPT, or Cursor seat required.
2. Feedback on the page — inline comments on the live artifact, not a side channel.
3. Any AI tool — you publish via MCP from whatever generated the HTML; the link is not locked to one vendor's share dialog.

Supporting details: email allowlist (not public by default), analytics on opens, and the same URL when you publish a revision.

Your AI made something useful. Docklet makes it usable. Publish AI-generated pages, guides, demos, and mini-sites as live links with comments, analytics, permissions, and version history — in-place right from your AI tool.

How to publish with Docklet

Two paths — both land on the same live URL:

1. From Claude chat (MCP) — Connect the Docklet connector (setup guide, endpoint https://app.docklet.io/mcp) and ask Claude to publish the artifact. Claude calls publish_website and returns the link.
2. From the Docklet console — Paste HTML or upload files, or use the API with a personal access token.

Set visibility to public, any signed-in user, or selected users (email allowlist — the usual default for client work). The Free plan includes the email allowlist and covers your first five Docklets. Pro is $4 per user per month and adds private visibility, a custom domain, and up to five versions with rollback.

A concrete client loop:

1. Publish the artifact to Docklet.
2. Allowlist two client email addresses.
3. They open the link, read the page, and leave comments.
4. You revise in Claude and republish — same URL, new version.

See a live example: ashley.docklets.io/q3-pricing/.

FAQ

How do I share a Claude artifact with a client without making it public?

Publish to Docklet and set visibility to selected users with your client's email addresses on the allowlist. They get a normal browser link — no Claude account, not indexed, not open to the world.

Does my client need a Claude account?

No. Docklet links open in any browser. Only the emails you allow can access a restricted Docklet.

Does the link change after I edit the artifact?

No. Ask Claude to update the existing Docklet (via update_website) or republish from the console. The URL stays the same; version history keeps prior revisions.

What if I just need a quick look, not a review loop?

Claude Publish is well suited for a fast public or in-org snapshot. A paste-and-host tool works when you only need a URL. Add Docklet when recipients should open without your AI tool, leave comments on the page, or you may publish from a different MCP client next week.

Does this work from ChatGPT or Perplexity?

Yes. Any MCP-connected tool can publish to Docklet the same way Claude does. You can also paste HTML in the Docklet console without MCP.

What does it cost?

Free ($0) covers five Docklets with public and selected-user visibility. Pro is $4 per user per month (private visibility, custom domain, five versions). Team is $9 per user per month. Enterprise is custom. Yearly billing saves 20%. See pricing for full details.

Claude, Claude.ai, and Anthropic are trademarks of Anthropic, PBC. ChatGPT is a trademark of OpenAI. Perplexity, Netlify, and other product names are trademarks of their respective owners. Docklet is not affiliated with, endorsed by, or sponsored by those companies. Product behavior cited here is based on public documentation as of August 2026 and may change.

← Back to the homepage