Anthropic's Claude Code Turns AI Sessions Into Live Shareable Dashboards
Claude Code artifacts can now call your MCP connectors at view time, letting each viewer pull their own live data without the creator re-running anything.
- New feature: Claude Code artifacts can now call MCP connectors at view time, pulling live data for each viewer using their own credentials.
- Per-viewer data isolation: Viewers only see data they have access to; the artifact creator does not need to re-run sessions to refresh content.
- 554 MCP integrations are available in Anthropic's connector directory, including GitHub, Slack, Jira, Sentry, Google Calendar, and more.
- Availability: MCP integration for artifacts is on Pro, Max, Team, and Enterprise plans; Claude Code artifacts specifically require Team or Enterprise.
- Hard limits: Artifacts are single static HTML pages (16 MiB max), no backend, no public sharing with live MCP data, and not available under CMEK/HIPAA/ZDR compliance configs.
- Competitive context: OpenAI's Codex "Sites" offers a fuller backend (databases, auth), while Claude's approach trades depth for zero-infrastructure speed.
Claude Code just got a meaningful upgrade to its artifacts feature. Anthropic has announced that Claude Code artifacts can now turn a session's work into a live, interactive, shareable HTML page that connects to multiple data sources and surfaces on a URL teammates can open instantly. The new twist: those artifacts can now call MCP connectors at view time, meaning the data refreshes for each viewer on demand using their own credentials.
The problem with static snapshots
Before this update, Claude Code artifacts were already useful for sharing session output. Claude would build an HTML artifact, connect it to MCP servers, and save it to the Live Artifacts tab in the sidebar, where a toggle enabled real-time data refresh. But the model was creator-centric: the person who built the artifact had to re-run their session to get fresh numbers, and sharing meant sharing a frozen snapshot.
The new capability flips that model entirely. Users authenticate with their Claude account and interact with their own instance of the artifact, with no API keys required and no costs to the creator. Each viewer's MCP connections supply the data, so a dashboard showing Jira tickets or Slack messages shows their Jira tickets and Slack messages, not the creator's.
How it actually works
MCP, or Model Context Protocol, is an open standard that lets Claude connect to external tools and data sources through a standardized interface. Think of it as a universal adapter layer. Claude Code can connect to hundreds of external tools and data sources through MCP. There are now 554 tracked MCP integrations across Anthropic's connector directory, organized across 30 categories.