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

What is the Display MCP server?

MCP (Model Context Protocol) lets Claude call external tools during a conversation. When you configure the Display MCP server, Claude gets four tools: publish, find, get, and delete.

When you say "publish this to my team," Claude calls publish() 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

Log in to Display → Settings → API Keys → Create new key. Copy it.

Step 2: Open Claude Desktop settings

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

Step 3: Add the Display 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 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 call publish(), 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 workspace 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 workspace 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. No individual configuration. No API key management for individual users.

What happens when Claude publishes

1. Claude detects the artifact in the conversation context (HTML, Markdown, or any supported format).
2. Claude calls publish(file_content, filename, metadata).
3. Display stores the content in your workspace.
4. A permanent URL is returned: https://[workspace].dsp.so/[artifact-id].
5. Claude includes the URL in its response.
6. 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 dashboard — 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."