dsh-mcp-market

Connecting a single MCP server to DeepSeek Harness Web used to mean opening cordis.patch.yml, cross-referencing vendor docs to assemble the JSON skeleton, filling in tokens and project IDs by hand, then refreshing or restarting to see the change. As the list grew, the YAML became a dense wall of repeated structures where one stray deletion could silently break a session. dsh-mcp-market moves the entire workflow into a visual panel in the sidebar, turning file-level editing into a guided click-and-paste experience.

The panel offers three paths: marketplace templates (Apifox public or self-hosted, Apipost cloud or self-hosted, MasterGo, Pixso remote or local) pre-fill a JSON skeleton in the editor while you still supply tokens and private addresses yourself; manual configuration accepts a full mcpServers JSON block in Claude Code .mcp.json format, with support for pasting multiple servers at once and inline // comments; and the My Services list lets you enable, disable, edit, delete, or inspect any entry in place, showing read-only cards for configurations that originate outside DSH. Every change is written into the managed region of cordis.patch.yml and hot-loaded by the DSH loader, so new servers connect and register their tools as mcp____ immediately without restarting dsh web.

It is built for teams and individual developers who run multiple MCP providers behind a DSH Web instance, whether that is an API gateway, a design-collaboration tool, or a remote rendering service. You no longer need to grep through YAML for a specific entry or cross-check an external spec every time you add a server. One panel, one hot-reload loop, done.