Dsh MCP Apps — Development skill for Claude Code

dsh-mcp-apps

MCP Apps support for [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness), packaged as ordinary Cordis plugins.

The project deliberately keeps the protocol host and each presentation surface separate. Installing the bundle adds two independent rows: a Host service that shares the existing MCP connection and a Web renderer that runs App HTML behind a double-iframe sandbox. One AppBridge session can move between inline, fullscreen, and picture-in-picture surfaces without remounting its iframe.

Which package should I install?

Goal	Install
Use Codex, Claude Code, Pi, or portable Agent Plugins in DSH, including their MCP Apps	`@openma/dsh-agents-plugins-bridge` only; it already carries MCP Apps
Add MCP Apps to a Web profile without the foreign-plugin bridge	@openma/dsh-mcp-apps

The standalone package and the Bridge use the same Host and Web runtime packages. Do not install both bundles into one profile just to get the renderer twice.

Install

dsh plugin --profile web add @openma/dsh-mcp-apps

From a local checkout, install dependencies and add only the root bundle:

npm install
dsh plugin --profile web add .

The full bundle is safe on a DSH composition that already provides `ctx.mcpApps` and the generated `remote.mcpApps` namespace: the fallback Host row becomes a no-op and the Web renderer reuses the existing Remote. If the active profile is known to include the official Host already, installing only the renderer is the minimal equivalent:

dsh plugin --profile web add ./packages/web

The renderer consumes a composition-provided Remote when present and mounts its checked-in descriptor only for the standalone fallback Host.

The bundle patch mounts one kernel:

- id: mcp-apps-bundle
  name: '@openma/dsh-mcp-apps'

That kernel owns two independent child rows, `mcp-apps-host` and `mcp-apps-web`. Both row