dsh-project-mcp-ui

Settings tab for dsh-project-mcp-manager. It lists the servers the loader will run, and writes only the managed mcp.yml for that scope. A same-name copy in another file stays as a note on that card. A non-yml row with a different name but the same command and arguments, or the same URL, is left off the list. Add MCP opens a form and writes the row. Fill from clipboard reads one JSON or YAML server into that form. MCP config stays beside it and opens the file for anything the form does not cover.

The default manager bundle includes this UI package automatically. Install only the manager into the profile you use:

dsh plugin --profile web add dsh-project-mcp-manager@latest
# Or, for the desktop app:
dsh plugin --profile desktop add dsh-project-mcp-manager@latest

The core-plus-UI bundle is included in source version 0.8.0; these npm examples apply after both 0.8.0 packages are published. A Git tag does not publish to npm. The manager depends on this package at the same exact version, and this package keeps its exact-version manager peer dependency. Both packages must be versioned and published together. This package no longer declares a standalone dsh.bundle and should not be selected separately in a profile.

The page is a Plugins settings tab, enabled by default. In the plugin manager, switch off the manager bundle's mcp-project-ui component to hide it, leaving mcp-project enabled; a profile patch override disabling that UI row also works. The loader keeps running. In headless mode there is no browser runtime or settings page. Without the dsh connection service, no UI routes are registered; its connection-scoped integration waits without blocking the core loader. The UI row itself can be active, and the connection integration is registered and cleaned up with that service's lifetime.

For local development, run pnpm install and pnpm run build in the repository root, then dsh plugin --profile web add link:<source>. The root build compiles core first and then the UI (host code and browser bundle); only the manager link is needed. Rebuild after source changes.

If the UI was installed separately, first install the manager bundle, then remove dsh-project-mcp-ui from the profile bundle selection (dsh.profile.bundles), keeping the manager selected. Optionally run dsh plugin --profile web remove dsh-project-mcp-ui afterwards to remove the direct UI dependency (use desktop for that profile); the manager's transitive UI dependency remains. An old direct UI version can take precedence over transitive resolution, so remove it (recommended) or align it to the manager's exact version before running the new bundle. Old bundle selections and direct dependencies are not promised to be cleaned up automatically.

If the old standalone UI bundle was disabled, preserve that intent before loading the new manager bundle with this profile patch row override; disabling the old bundle alone does not stop the new default-enabled UI component:

- id: mcp-project-ui
  disabled: true

Usage guide: settings page (中文).