Share a Claude artifact without a Claude account

The short answer

Artifact Publisher hosts one self-contained HTML document at a stable link. If you give it the HTML of a Claude artifact, the link it returns is unlisted by default: anyone who has the URL can open it in a browser, with no account. In short:

1. Create a workspace in your account and copy the publisher key. It is shown once.
2. Connect an MCP client to https://app.artifactpublisher.com/mcp with that key.
3. Ask the client to publish the artifact's HTML.
4. Send the link from the result.

What Claude's own sharing requires of the recipient

The Claude Help Center article "Share artifacts" (support.claude.com, article 9547008; shown as text because this site links to no third-party pages) says that, on its current plans, everyone needs a Claude account to open a shared artifact, even with the link. It names one exception: a legacy artifact published from a chat. We read it on 17 October 2026. Sharing options differ by plan and change over time, so check that article for your plan. Artifact Publisher is a separate service: it does not read your Claude account and does not copy artifacts out of Claude.

Get the HTML to an MCP client

Artifact Publisher takes HTML as text. It has to be one document with everything inline: styles, scripts, images and data. Ask Claude for the page as a single self-contained HTML file, or ask an agent that is already connected to the MCP server to build and publish it in one step. The document can be up to 10 MiB of UTF-8.

Setup snippets for Claude Code, Claude Desktop, Cursor, Codex CLI, VS Code and Windsurf are in thequickstart. In Claude Desktop the route uses a custom connector with a request header. The quickstart notes that request headers are in beta and not available on every account, so confirm it works on yours.

Publish it

Once the client is connected, one instruction is enough:

Publish this HTML as an unlisted artifact titled "Q3 plan".

The client calls publish_artifact with title and html. The result has the share link in its url field, in the form https://app.artifactpublisher.com/artifact/<slug>. Keep the publisher key out of prompts, repositories and artifacts.

Choose who can open it

For people without accounts, use unlisted. To change the mode later without a new version, callset_artifact_access:

{ "artifact_id": "<artifact_id>", "visibility": "allowlist", "allowed_emails": ["reviewer@example.com"] }

Unlisted is not authenticated. Anyone who holds the link can open it, including whoever it is forwarded to. If identity matters, use private or allowlist.

Update it or take it back

update_artifact adds a new immutable version behind the same link. It needsexpected_version, which must equal the current version. Recipients keep using the link they already have. revoke_artifact stops serving the artifact. It cannot recall a copy someone already saved.

Limits to know before you share

• One HTML document, up to 10 MiB of UTF-8. It is not a general web host.
• The page runs in a sandboxed iframe with no network access. Fonts, images, scripts and APIs that load from other sites will not load, and a page that calls another service from its own code will not work. Links a reader clicks still open, in a new tab.
• A Claude artifact that relies on Claude features, connectors or shared storage will not work once its HTML is published here. The page has no network access and no connection to your Claude account.
• The publisher needs an account; the recipient of an unlisted or public link does not.
• Artifact HTML is untrusted and isolated on its own origin. That limits what it can reach. It is not an absolute guarantee.

Common questions

Does the recipient need an account?

Not for unlisted or public links. private needs your sign-in.allowlist needs a signed-in account whose primary email is on the list.

Where is the data stored?

Artifact documents and metadata are stored in Cloudflare's EU jurisdiction. Requests can be processed at any Cloudflare location, including outside the EU, on the way. Sign-in is handled by Clerk, a US sub-processor. Theprivacy policy has the details.

Is it certified or audited?

No compliance certification, independent audit or penetration test is claimed.

Next

• Create a workspace and publish your first artifact
• Quickstart and FAQ
• Publish HTML over MCP: client setup, tools and limits
• MCP integration (access modes) and how viewing is sandboxed
• Beta terms