mcp-deliverable

Managing MCP servers in DeepSeek Harness used to mean repeatedly editing the cordis.patch.yml file under your profile: tweaking a stdio working directory or swapping a Streamable HTTP request header all required hand-typed YAML followed by a restart, with no easy way to verify that the Loader actually registered the tools you expected. mcp-deliverable moves that entire workflow into Web Settings → Plugins, turning configuration into a form-filling experience.

The plugin operates in three layers. The Host Remote handles reading, atomic writes, and deletion of the current profile's MCP configuration while displaying live Loader and tool-registration status. The Web settings page covers both stdio and Streamable HTTP servers, letting you visually edit parameters, environment variables, working directories, request headers, call timeouts, failure strategies, and reconnect policies. Invalid configurations and dynamic !!js expressions remain visible and removable on the page, yet the raw expressions are never shipped to the browser. The Bundle ships self-contained Typert descriptors and a browser product, built by the prepare script at install time with no need for a sibling Harness checkout. On the security side, literal env and header values are read and written by the trusted Host settings client, while secrets should stay in environment-backed !!js expressions so credentials never leak into the browser or a plain-text config file.

This plugin is ideal for users running multiple MCP tools in DeepSeek Harness who want to stop hand-editing YAML. Whether you are wiring up one or two stdio servers for local experiments or maintaining several Streamable HTTP remote services with fine-grained timeout and reconnect control, it makes the configuration step more intuitive and far less error-prone.