AI Agent Hub
Back to plugins
🖥️

dsh-skills-mcp-group-manager

Client Updated 2026.09.04

Run the following command in DeepSeek Harness:

dsh plugin install SeverusZh/dsh-skills-mcp-group-manager

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install SeverusZh/dsh-skills-mcp-group-manager in DeepSeek Harness to install this plugin; source code is available at https://github.com/SeverusZh/dsh-skills-mcp-group-manager

About this plugin

As your Skills and MCP servers multiply in DSH, managing them one by one becomes tedious and context injection starts to feel out of control. dsh-skills-mcp-group-manager folds grouping, filtering, and toggling into a single floating left panel: create, rename, and collapse groups; batch-add or remove members after a search filter; only Skills inside enabled groups are injected into the model catalog (union, deduplicated, real-time refresh), while ungrouped ones stay out by default. Every MCP server, whether from profile config or user-added, is independently toggleable, dynamically mounted, and atomically persisted so it survives restarts. No external packages, no build step, no layout changes.

It is built for two kinds of users: developers whose Skill library has grown large enough to warrant per-project or per-scenario grouping with selective injection, and users juggling multiple MCP servers who need fine-grained control over which ones participate in a given session. The plugin overlays as a pure floating panel without touching DSH product layout. Uninstalling it runs a postuninstall script that removes the entire state directory, so all grouping and MCP configuration is cleaned up with the plugin in one shot.

Use Cases

  • Group a growing Skill library by project or scenario and inject only the skills the current task needs
  • Run multiple MCP servers side by side and toggle each one independently per session
  • Enforce consistent Skill visibility for the model across a shared DSH team environment

Best For

  • DSH users whose Skill library has outgrown flat management and needs scenario-based groups
  • Developers juggling multiple MCP servers who need fine-grained per-session control
  • Users who prefer a lightweight floating panel over modifying DSH product layout