DeepSeek Harness Plugin

borgez/dsh-project-mcp

Category Tools & Capabilities Added 2026-10-16

Per-project MCP servers: a project declares servers in its own documents (`.dsh/mcp.json` by default; the local and global file lists are settings), and they are mounted only for the sessions working in that project — on the first turn of a session, released when it goes idle. A right-sidebar tab and a Settings page list each project with a live session, the status of every server and the session holding each mount, with `Sync` / `Retry` / `Release`, an `enabled` switch and an editor over one existing entry; a per-project tool policy (`disclosure` / `direct` / `off`) with pins and `mcp_search_tools` decides what the model sees; `${VAR}` references resolve through the project `.env` files and the credentials file; per-server call counters outlive the sessions that produced them.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:borgez/dsh-project-mcp

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.