The short version: a Claude Code artifact — the live web page Claude publishes from a session to a private URL on claude.ai — used to be a snapshot, frozen with whatever data the session had when it built the page. As of Claude Code v2.1.209, a published artifact can call MCP connectors every time someone opens it, and each call runs through the viewer's own connections. That single change turns "here's a dashboard I made" into "here's a live internal tool that shows you your data" — with no backend and no deploy.

What it is · who it's for · how to start · what it costs#

The one prompt that builds it#

Name the connector and the data you want, and say you want it fetched on load:

Build a dashboard artifact of our open pull requests that
pulls the live list through my GitHub connector when the
page loads. Refresh it every 5 minutes, and show a fallback
line naming the connector for anyone who hasn't connected it.

When Claude publishes, it declares which connectors the page may call — and the page is boxed in: it can't call anything outside that declaration. The page fetches on load and can refresh on an interval or via a refresh control you ask for. Responses are cached in the viewer's browser, so reopening renders instantly from cache, then updates with fresh results.

The part that makes it actually useful: per-viewer data#

This is the design decision worth understanding before you build. When a published page calls a connector, the call uses the account of the person viewing the page — not yours.

That's why the feature is more than a convenience: a single artifact becomes a genuinely multi-tenant internal tool, and you never centralize anyone's access.

Constraints to design around#

Read these before you promise a teammate a link:

Why this matters for a small team#

The gap this closes is the one between a throwaway dashboard and an internal tool. Building the second used to mean a backend, auth, hosting, and a deploy pipeline — real work for a status board nobody looks at after a week. Now the same page that Claude would have published as a static snapshot can pull live data, scope it per viewer, and let people act on it, with zero infrastructure on your side. For a solo founder, that's the difference between "I'll build that admin panel someday" and "I built it in one prompt this afternoon." If you already lean on Claude Code, connect the MCP servers you care about and point an artifact at them — the throwaway just became load-bearing.