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.
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 has no built-in publish step. Claude's web Publish button doesn't exist in the CLI. Claude org sharing requires Claude seats for every viewer. Screenshots destroy the interactivity you just built.
The artifact took 60 seconds to generate. Sharing it takes an hour of workarounds — or it doesn't happen.
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.
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"
}
}
}Any HTML file Claude Code writes to disk. That includes:
For directory output (multiple files): dsp publish ./output/ — serves index.html at the root, all assets resolved.
| 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 |
Free — one-time password auth, 50MB, unlimited viewers
Pro ($49/month) — Google + Microsoft SSO, 25GB, custom domain, unlimited viewers
The free tier covers individual use with email OTP. Pro adds one-click Google/Microsoft SSO once the team is on board.
Publish your first Claude Code artifact free →
Authentication. 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.
Comments. Inline comments on every artifact. Your agent reads them via MCP, updates the document, resolves the thread. The artifact stays a living document, not a one-shot screenshot.
Publish in 15 seconds. dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Permanent URLs. Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
Unlimited viewers. No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Any agent. Claude Code, Codex, and Cursor all work, along with anything else that creates HTML or Markdown output. Not locked to one provider.
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.
Yes. Claude Code writes HTML to disk. dsp publish ./file.html publishes any file on disk, regardless of which tool generated it.
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.
Yes. Run dsp publish ./updated-file.html --name "q1-architecture" with the same name to overwrite. The URL stays the same — everyone who bookmarked or shared it sees the updated version.
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.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).