Does the MCP server see my conversation content?

Only the content you explicitly ask Claude to publish. The MCP server receives the file content when Claude invokes the `publish` tool. It does not have access to the rest of your conversation history, other artifacts, or any data you haven't chosen to publish.

What formats can Claude publish?

HTML, Markdown, and plain text. Claude Code artifacts are typically self-contained HTML with inlined CSS and JS, which publish and render perfectly. Markdown is rendered to HTML at the display.dev viewer.

Can Claude update an artifact after it's published?

Yes. Ask Claude to "update the published version" and it will fetch the current version, then invoke `publish` with the artifact's `short_id`, that `base_version`, and the updated content. The URL stays the same, and viewers who previously bookmarked or shared the link will see the updated version.

Is there a free tier for MCP publishing?

Yes. The free tier supports one-time password authentication, where viewers receive a one-time login link via email. The Pro plan (€49/month) adds Google and Microsoft SSO (one-click authentication, no email check). MCP publishing works on both tiers.

How does this compare to Claude's built-in Publish button?

Claude's Publish button (web UI only) creates a public URL with no company restriction. Claude Code Artifacts can publish private pages on Pro, Max, Team, and Enterprise, but on Pro and Max they stay private to you, sharing is Team/Enterprise-only, viewing a shared page requires a Claude seat in your org, and the source has to be Claude. The display.dev MCP integration creates a company-gated URL that any `@yourcompany.com` email holder can open without a Claude seat, and it works the same from Claude Code, Cursor, Codex, and CI.

How to Publish Claude Desktop Artifacts to Your Team (MCP Setup Guide)

What is the display.dev MCP server?

MCP (Model Context Protocol) lets Claude invoke external tools during a conversation. When you configure the display.dev MCP server, Claude gets seven tools whose names match the dsp CLI subcommands one-to-one: publish, share, rename, find, get, export, and delete.

When you say "publish this to my team," Claude invokes the publish tool with the current artifact's content, receives a company-gated URL back, and returns it in the conversation. You get a permanent URL that only people with your company email can access, without leaving Claude Desktop, opening a terminal, or managing files.

Who this is for

Product managers and analysts who create content in Claude Desktop (presentations, competitive analyses, reports) and need to share it with teammates without a public link.

Executives and non-technical users who want to share Claude output as easily as they send a Slack message.

Engineering leads who want to deploy the MCP configuration to their entire team via MDM, so every teammate gets publishing capability in Claude Desktop without individual setup.

Individual setup (5 minutes)

Step 1: Get your API key

Step 2: Open Claude Desktop settings

Claude Desktop → Settings → MCP Servers (or Developer → MCP Configuration)

Step 3: Add the display.dev MCP server

{
  "mcpServers": {
    "display-dev": {
      "url": "https://mcp.display.dev",
      "apiKey": "your-api-key-here"
    }
  }
}

Step 4: Restart Claude Desktop

Close and reopen the app. The display.dev tools are now available in every conversation.

Step 5: Try it

Open a conversation. Create something. Ask Claude to publish it:

"Publish this competitive analysis to my team."

Claude will invoke the publish tool, and within a few seconds return:

"Published. Your team can access it at: https://acme.dsp.so/competitive-analysis-q1"

That URL requires company email authentication. Anyone with a @yourcompany.com Google or Microsoft account can view it.

Team-wide deployment (via MDM: Jamf, Intune)

For engineering leads deploying to an entire organization:

Step 1: Create an org-level API key

In display.dev organization settings, create an API key scoped to your organization (not a personal key). This key is used for all MCP-published artifacts and appears in the audit log as organization activity.

Step 2: Create the MCP configuration file

{
  "mcpServers": {
    "display-dev": {
      "url": "https://mcp.display.dev",
      "apiKey": "org-api-key-here"
    }
  }
}

Step 3: Deploy via MDM

The Claude Desktop MCP configuration file lives at:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Deploy the configuration to this path on all managed devices. Users receive the publishing capability without any individual setup.

Result: Every teammate with Claude Desktop can now say "publish this to my team" and get a company-gated URL, with no individual configuration or per-user API key management.

What happens when Claude publishes

Claude detects the artifact in the conversation context (HTML, Markdown, or any supported format).
Claude invokes the publish tool with the file content, name, and metadata.
display.dev stores the content in your organization.
A permanent URL is returned: https://[organization].dsp.so/[artifact-id].
Claude includes the URL in its response.
Viewers click the link, authenticate with their company Google or Microsoft email once, and see the full page.

The published artifact is accessible from your display.dev dashboard, where you can view analytics, update it, or delete it at any time.

What you can say to Claude

You don't need specific syntax. Claude understands intent. Any of these work:

"Publish this to my team."
"Share this competitive analysis with the company."
"Create a URL for this report that only people with @acme.com emails can access."
"Publish this and give me the link."
"Make this available to my colleagues."

For more control:

"Publish this with the title 'Q1 Architecture Review'."
"Publish this publicly so anyone can view it."
"Publish this and set it to expire in 30 days."