Claude Cowork

Connect Display.dev as a remote custom connector, then enable it in Cowork from Claude on the web, Claude Desktop, or the mobile app.

Cowork is a mode inside Claude, not a separate app. Its tasks run remotely by default, so the agent loop and code execution stay in Anthropic's cloud whichever Claude app you use to start the task.

Claude Cowork requires a paid Claude plan. For cloud code execution to transfer an existing file, code execution, file creation, and network access must be available. An Owner may control these capabilities for a Team or Enterprise organization.

Add Display.dev to an individual Claude account

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.
6. On the Display.dev 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.
7. When Claude.ai returns to Display.dev and shows Disconnect and Tool permissions, the connection is complete.

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

Add Display.dev to a Team or Enterprise organization

An Owner or Primary Owner must add the connector first:

1. Open Organization settings → Connectors.
2. Select Add, hover over Custom, then choose Web.
3. Enter https://api.display.dev/v1/mcp and select Add.

Each member then opens Customize → Connectors, finds Display.dev, and selects Connect to complete their own authorization.

Start a Cowork cloud session

1. Open Claude on the web, Claude Desktop, or the Claude mobile app.
2. Select Cowork in the message box and start a task.
3. Open + → Connectors and enable Display.dev for the task.
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 an existing file

Ask Cowork 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:

Publish the existing file report.html through Display.dev. Before you start,
ask me to choose its visibility.
Use staged remote MCP publishing. Do not print or log the upload URL,
upload ID, or file contents. Return only the published artifact result.

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

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

Fix connection or publishing errors

• 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 Cowork task and check the tools again.
• The file transfer cannot reach its destination – confirm that network access is enabled for Cowork code execution. Team and Enterprise policies may restrict outgoing connections.
• The transfer expires or becomes unavailable – ask Cowork to start again with a new create_upload. Do not reuse the previous transfer.

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