How dsh-plugin works
DeepSeek Harness loads dsh-plugin as an integration layer for CloudBase. The package combines an MCP server, Agent Skills and Hooks, then exposes CloudBase operations through tools named mcp__cloudbase__*. The README describes operations for login, data queries and changes, functions, hosting, storage, logs and deployment. It also describes a DB/Storage/Auth panel for the DeepSeek Harness interface.
Authentication uses a device-code login flow. The toolkit connects to a CloudBase environment supplied by the developer; the README does not document a default environment or a default region. Sensitive actions still require review before they are allowed to proceed.
Configuring dsh-plugin
The README identifies these configuration values:
| Identifier |
Purpose |
lang |
Sets the instance-level tool language. |
auth.site |
Selects the authentication site. |
auth.region |
Selects the authentication region. |
envId |
Identifies the CloudBase environment. |
region |
Selects the CloudBase region. |
site |
Selects the CloudBase site. |
envId, region and site can be supplied through cloudbaserc.json as field-level fallbacks. Values may be literals or expressions such as {{env.KEY}}. The README does not specify defaults for these values.
CloudBase operations
The MCP toolset can scaffold and deploy full-stack applications from chat, query data and render results as table cards with paging, sorting and CSV export. It can also manage database, storage, authentication, functions and hosting resources, read logs, and preview a deployment on its CloudBase domain.
Requirements and limits
A CloudBase environment is required. dsh-plugin operates through the agent’s permissions and includes a terminal surface for the MCP tooling, so proposed sensitive changes should be confirmed. Developers who only need CloudBase guidance rather than operational access may prefer the separate Skills collection described by the README.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub