display.dev for Claude Code
Claude creates the artifact. display.dev is where your company sees it. One command turns your Claude Code HTML output into a permanent URL that only people with your company email can access. No Claude seats required for viewers. And because display.dev works with any agent, the URL outlives your tool choice – switch to Codex or Cursor later and everything you published stays exactly where it is.
Claude Code generates HTML. Then what?
Claude Code writes HTML files to disk. Architecture proposals. Competitive analyses. Visual reports. Interactive presentations. All self-contained. All beautifully rendered.
All stuck on your local machine.
Claude Code Artifacts can turn session work into an interactive page, but only people with an authenticated Claude Team or Enterprise seat can open it. The source has to be Claude. There is no external or public sharing and no comments. So your PM, your exec, and your client – everyone without a Claude seat – still can't see it.
display.dev opens viewing to anyone with their company Google or Microsoft login, no Claude seat required. It works from any agent, so the URL outlives your tool choice. And comments from anyone feed straight back to the agent.
The artifact took 60 seconds to generate. Getting it in front of the people who need it shouldn't take an hour of workarounds.
Three steps. Fifteen seconds.
Step 1: Install the CLI once
npm install -g @displaydev/cliStep 2: Publish
dsp publish ./output.html --name "q1-architecture"Step 3: Share the URL
Paste it in Slack, Notion, Jira, or email. The link is permanent.
What your teammates see: They click the link. They authenticate with their company Google or Microsoft email – one time, five seconds. They see the full interactive artifact: charts, animations, tabs, all of it. No app to install. No account to create.
Or: say it in Claude
Configure the display.dev MCP server once. After that, in any Claude conversation:
"Publish this architecture proposal to my team."
Claude invokes the publish tool, gets back a company-gated URL, and returns it in the conversation. No terminal. Works in Claude Desktop, Claude Code (with MCP), and any Claude-compatible client.
// Claude Desktop config (Settings → MCP Servers)
{
"mcpServers": {
"display-dev": {
"url": "https://mcp.display.dev",
"apiKey": "your-api-key"
}
}
}Everything Claude Code generates
Any HTML file Claude Code writes to disk. That includes:
- Architecture diagrams with D3, Mermaid, or custom SVG
- Competitive analyses with sortable tables and interactive filters
- Visual reports with charts, animated transitions, and data grids
- Interactive presentations with tabs, slides, and dynamic content
- Dashboards with live-looking data and rich layouts
- Technical specs rendered as polished HTML documents
For directory output (multiple files): dsp publish ./output/ – serves index.html at the root, all assets resolved.
Claude Code sharing options compared
| Option | Non-engineer viewers | Company auth | Interactivity | Time | Cost |
|---|---|---|---|---|---|
| Screenshot | ✅ (degraded) | – | ❌ | 10 sec | $0 |
| Claude org share | ❌ (needs seats) | ✅ | ✅ | 5 sec | $25+/seat/mo |
| GitHub Pages | ❌ | ❌ / $2,100/mo | ✅ | 5–30 min | $0 / $2,100/mo |
| Vercel + SSO | ❌ | ✅ | ✅ | 20+ min | $320+/mo |
| display.dev | ✅ | ✅ | ✅ | 15 sec | $49/mo flat |
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Private artifacts
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 90 days audit logs
For compliance-driven organizations.
From $499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: Private artifacts
- Included: 365 days audit logs
The free tier covers individual use with email OTP. Pro adds one-click Google/Microsoft SSO once the team is on board.
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays a living document, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Claude Code, Codex, and Cursor all work, along with anything else that creates HTML or Markdown output.
What teams say
"We use it to share and collaborate on markdown and HTML artifacts, and it's helped us work together more seamlessly in this weird new agentic coding era. Our whole 7-person team uses it."
– Max Wood, CEO, Indigo Engineering. Read the story →
Common questions.
Do my teammates need Claude accounts to view the artifact?
No. display.dev authentication is based on your company's Google or Microsoft email – the same account they use for everything else. No Claude subscription required for viewers.
Does this work with Claude Code CLI, not just Claude's web UI?
Yes. Claude Code writes HTML to disk. dsp publish ./file.html publishes any file on disk, regardless of which tool generated it.
What if my Claude Code output is a directory of files, not a single HTML file?
Run dsp publish ./dist/ – display.dev serves the whole directory at a single URL, with index.html as the root and all relative asset paths resolved.
Can I update a published artifact?
Yes. Fetch the current version, then run dsp publish ./updated-file.html --id <shortId> --base-version <currentVersion>. The URL stays the same – everyone who bookmarked or shared it sees the updated version.
Does the MCP version work from Claude Code CLI?
display.dev's MCP server works in any Claude-compatible MCP client. Claude Code's CLI supports MCP. Configure it in your ~/.claude/settings.json the same way you'd configure any MCP tool.
What about Claude Desktop artifacts specifically?
See /share-claude-artifact – same product, framed for Claude Desktop and the web app, including the inline comments your agent reads back via MCP.
Is my agent's work attributed to me?
Yes. When Claude Code publishes through display.dev it is recorded as "claude-code on behalf of you", in the comment thread and the audit log. See how identity works.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).