Claude Live Artifacts: What They Are and How to Share Them

Live artifacts are Claude artifacts connected to real-time data sources via MCP (Model Context Protocol). Where a standard artifact captures a snapshot of data at the moment Claude generates it, a live artifact fetches fresh data each time it loads — making it useful for dashboards, status pages, analytics views, and anything where the data changes between sessions. Live artifacts are available in Claude Cowork on Pro and above plans.

For background on standard artifacts, see the complete Claude artifacts guide.

Last updated: October 2026

August 2026 update: Anthropic changed how live artifacts work on August 19, 2026. Artifacts created in Cowork before that date remain as legacy live artifacts — MCP data connections still work, but sharing is now internal only (no external public links via Anthropic's Publish). Artifacts created in Cowork after August 19 work like standard artifacts for sharing purposes. The current solution for publicly sharing real-time artifacts is ShareDuo's MCP server, covered below. The rest of this page covers both the original feature and the current state.

What is the difference between live artifacts and regular artifacts?

A standard Claude artifact is static. If you ask Claude to build a sales dashboard from a CSV you pasted into the chat, the numbers in that dashboard are fixed at whatever was in the CSV. The artifact doesn't update when the underlying data changes.

A live artifact has an active MCP connection. Instead of using data Claude processed during generation, the artifact calls an MCP server at load time and pulls current data. Open it today and it shows today's numbers. Open it tomorrow and it shows tomorrow's. The artifact's structure and logic stay constant; only the data changes.

What can you build with Claude live artifacts?

Live artifacts are well suited to use cases where freshness matters:

• Real-time dashboards — pull metrics from a database or analytics API on each load
• Status pages — show current system health, uptime, or incident state
• Analytics views — display live campaign, sales, or product data without manual refresh
• Live data tables — query a database and render results as a formatted table
• Inventory or pricing displays — show current stock levels or prices from a live source

The constraint is that the data source must be accessible via an MCP server. If your data lives in a database, API, or service that has an MCP connector, you can wire it to a live artifact. If it's in a spreadsheet you update manually, a standard artifact with periodic regeneration is usually simpler.

How to create a live artifact

Live artifacts require Claude Cowork (Pro or above) and an MCP server connection. Here's the setup flow:

1. Enable Claude Cowork — available on Pro and Team plans. Open a Cowork session from the Claude sidebar.
2. Connect an MCP server — in Cowork settings, add the MCP server URL for your data source. If the MCP server requires auth, you'll provide credentials here.
3. Describe the artifact — in the Cowork chat, tell Claude what you want to build and which MCP-connected data to use. Example: "Build a dashboard showing this week's signups and revenue, pulling from the analytics MCP server."
4. Claude generates the artifact — the artifact is created with live MCP data bindings. A preview loads with the current data.
5. Publish or share — use the Publish button the same way you would for a standard artifact. See what Publish does for details on sharing options.

Live artifacts vs standard artifacts

	Standard Artifact	Live Artifact
Data	Snapshot at creation time	Real-time via MCP
Plan required	Free	Pro or above
Publish as public link	Yes	Internal only (legacy, pre-Aug 2026); via ShareDuo MCP for new
Requires MCP server	No	Yes
Static HTML export	Yes	Limited

One practical note on static HTML export: a standard artifact downloads as a self-contained HTML file with all data baked in. A live artifact's HTML skeleton can be exported, but the live data connections won't function outside of Claude's MCP environment — the artifact needs the MCP server to be running and accessible to fetch its data.

Can you share a live artifact with someone who doesn't have Claude?

Before August 19, 2026: Yes — Anthropic's native Publish button created a public link and anyone could view the artifact without a Claude account.

After August 19, 2026: Legacy live artifacts (created before that date in Cowork) now support internal sharing only — Anthropic removed the external public link option for them. New artifacts created in Cowork after August 19 work like standard artifacts and follow your plan's normal sharing rules (Free/Pro/Max chat artifacts can still be published publicly; Team and Enterprise require a Claude account to view).

The ShareDuo path (the current solution): ShareDuo's MCP server fills this gap. From inside a Claude Cowork session, connect the ShareDuo MCP server, then ask Claude to push the artifact to ShareDuo. Claude calls push_artifact, uploads the HTML, and returns a public URL that anyone can open — no Claude account required. You can set expiry windows, password protection, and view analytics as part of the push call, all without leaving the conversation. This is now the standard path for teams publishing real-time dashboard artifacts publicly.

How ShareDuo's MCP server works

ShareDuo has its own MCP server at mcp.shareduo.com. It exposes two tools — push_artifact and delete_artifact — that let Claude push artifacts directly to ShareDuo from inside a Cowork conversation, without manually downloading and uploading HTML.

The workflow: in Claude Cowork, you connect the ShareDuo MCP server. When you're happy with an artifact, you ask Claude to push it to ShareDuo. Claude calls push_artifact, which uploads the HTML to ShareDuo and returns a public URL. You can set expiry windows, password protection, and other options as part of the push call — all without leaving the conversation.

The resulting ShareDuo link works the same as any other ShareDuo link: publicly accessible, no account required for viewers, with noindex and view analytics built in. For context on how other AI tools handle artifacts and sharing, see the comparison with Grok Studio.

How to export a live artifact

You can download the HTML of a live artifact the same way as a standard one — use the download icon in the artifact pane. The exported file contains the artifact's structure and layout with the last-loaded data baked in as a static snapshot. The MCP data connections don't travel with the file; the exported version won't refresh when opened in a browser outside Claude.

For a version that stays live and publicly accessible, the ShareDuo MCP route above is the better option: push the artifact from Cowork, get a stable public URL, and push an updated version at any time without changing the link. See how to export any Claude artifact for the full walkthrough on both download options.