Skip to content

Claude code execution

Publish work, including large existing files, from Claude's code execution or a Cowork task.

On this page

Connect Display so Claude can publish work it creates with code execution and return its link. Each published piece of work is an artifact. Add Display from Claude's connector directory, then enable it from Claude on the web, Claude Desktop, or the mobile app.

Claude's code execution runs in Anthropic's cloud, whichever Claude app you use. On Pro and Max, Cowork is part of Claude, so this applies to any conversation. On Team, and on Enterprise until an admin turns on Chat and Cowork unified (beta), Cowork is still a separate mode and this applies to Cowork tasks.

Publishing larger existing files requires Claude's code execution to reach api.display.dev.

Use the Quickstart setup prompt to have your agent guide you, or follow the steps below. Complete any sign-in or approval steps yourself.

Add Display to an individual Claude account

Personal Claude Pro and Max accounts can use the connector for inline publishing, but Claude cannot transfer large existing files because these accounts cannot allow api.display.dev for cloud code execution. Large staged uploads require a Claude Team or Enterprise organization configured as described below.

  1. Open Display in Claude's connector directory. Claude labels it Community: Anthropic screens directory connectors but has not reviewed this one in depth.
  2. Select Connect.
  3. On the Display authorization screen, confirm that Redirects to shows claude.ai, review the requested access, then select Authorize Claude. If the redirect host is different, select Cancel.
  4. When Claude shows Disconnect and Tool permissions for Display, the connection is complete.

To add it by URL instead:

  1. In Claude.ai, select Customize in the sidebar, then select Connectors.
  2. Select Add → Add custom connector.
  3. Enter Display.dev in Name and https://api.display.dev/v1/mcp in Remote MCP server URL.
  4. Under Advanced settings, leave OAuth Client ID and OAuth Client Secret empty, then select Add.
  5. On the Display.dev connector page, select Connect, then confirm the redirect host and select Authorize Claude as described above.

The connector also runs through Anthropic's cloud. Claude's code execution does not need a local MCP server. Keep Claude Desktop open only when the task needs a local file, browser, or computer.

Add Display to a Claude Team or Enterprise organization

An Owner or Primary Owner adds Display for the organization first: open Organization settings → Connectors, find Display in the directory, and add it.

Each member then opens the Display listing and selects Connect to complete their own authorization. A member without permission to add connectors sees Request instead, which asks the organization's Owners to add it.

To add it by URL instead, an Owner selects Add under Organization settings → Connectors, hovers over Custom, chooses Web, and enters https://api.display.dev/v1/mcp. Members then open Customize → Connectors, find Display.dev, and select Connect.

For staged file publishing, an Owner or Primary Owner must also:

  1. Open Organization settings → Capabilities → Code execution.
  2. Under Additional allowed domains, add api.display.dev.
  3. Start a new conversation or Cowork task after the policy change.

The connector and code execution use separate network paths. Connecting Display does not allow Claude's code execution to reach api.display.dev.

Enable Display in a conversation

  1. Open Claude on the web, Claude Desktop, or the Claude mobile app.
  2. Start a conversation. Where Cowork is still a separate mode, select Cowork in the message box and start a task.
  3. Open + → Connectors and enable Display.dev.
  4. Ask Claude to list the available Display.dev tools without calling them.

Confirm that both publish and create_upload appear. This verifies the connection without creating an artifact.

Publish your first artifact

Once Display's tools are available, use the first-publish example to create a Private sample and open its link. Then see Publish with your agent to publish your own work and choose who can open it.

Publish an existing file

Ask Claude to use staged publishing when the HTML or Markdown file already exists in its code-execution environment or is too large for a safe inline tool call:

text
Publish the existing file report.html through Display. Before you start,
ask me to choose its visibility.
Keep the source in code execution and use staged publishing if needed. Return
the artifact link without temporary upload credentials or source contents.

Claude measures the file, transfers its raw bytes, then calls publish. The temporary transfer expires after 15 minutes. The per-artifact limit is 10 MB on Free and 50 MB on Solo, Team, Business, and Enterprise.

For small HTML or Markdown generated directly in the conversation, Claude may call publish with inline content instead.

On personal Claude Pro or Max, Claude can publish smaller files inline through MCP. For a larger existing file, download it from the conversation, then run the Display CLI from your terminal (dsp publish ./report.html) or publish it through the Display dashboard. If the file is already on your computer, use it there directly.

Fix connection or publishing errors

  • Claude asks to install a skill or CLI – Claude's Display.dev connector tools run through Claude's remote connector service, while commands, scripts, and staged file transfers run inside Claude's code execution. Do not install the Display skill or CLI there. Add Display.dev under Customize → Connectors, complete authorization, start a new conversation or Cowork task, then enable Display.dev under + → Connectors. On Claude Team or Enterprise, an Owner or Primary Owner must add the connector to the organization first.
  • The connector returns 401 – open Customize → Connectors, disconnect Display.dev, then connect it again.
  • create_upload is missing – reconnect Display.dev, then start a new conversation or Cowork task and check the tools again.
  • Publishing fails with curl: (56) … response 403 or API returned 000 – Claude tried to publish from code execution. For small HTML or Markdown generated in the task, ask Claude to use the Display.dev connector's publish tool with inline content. For a large existing file on Claude Team or Enterprise, follow the staged file transfer recovery below. On personal Claude Pro or Max, download the file from the conversation, then run the Display CLI from your terminal (dsp publish ./report.html) or publish it through the Display dashboard.
  • A staged file transfer cannot reach api.display.dev – on Claude Team or Enterprise, add api.display.dev under the organization's code-execution allowlist, then start a new conversation or Cowork task. Personal Claude Pro and Max cannot currently add this domain.
  • The transfer expires or becomes unavailable – ask Claude to start again with a new create_upload. Do not reuse the previous transfer.

See MCP tools for the complete tool inventory and staged-publishing contract.

Was this page helpful?