dsh-plugins MCP server
Commit Oct 18, 2026Extends DeepSeek Harness with an MCP hub, Opfield instance integration, and multi-root workspace support.
Also known as opfield/dsh-plugins
- Stars
- 2
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 18, 2026
- License
- MIT
What is dsh-plugins MCP?
dsh-plugins extends DeepSeek Harness with an MCP hub, Opfield instance integration, and multi-root workspace support.
Summary generated from the project's README
About dsh-plugins MCP server
Expanding the capabilities of DeepSeek Harness is what these plugins accomplish through three distinct packages. Developers can use the MCP Hub to centralize all MCP servers in one location, allowing for eager, lazy, or automatic tool exposure. This hub supports OAuth for HTTP servers and can directly launch npx packages, making it compatible with any MCP server.
Users can also integrate Opfield instances as MCP servers to access models with automatic inference token and model sync. This specific integration requires the MCP Hub and provides components for budget management, prompt-cache timers, and a /compact command. For those managing complex projects, the multi-repo package enables multi-root workspaces by attaching additional repositories to a workspace. These attached roots become writable via workspace-write, appear in model context through AGENTS.md, and can be edited using the composer or the /roots command.
What you can do with it
- 1Centralize multiple MCP serversConsolidate various MCP servers into a single hub with flexible tool exposure settings.
- 2Manage Opfield model instancesConnect to Opfield instances to utilize synchronized models and manage inference budgets.
- 3Work across multiple repositoriesAttach and edit multiple repository roots within a single workspace context.
Written from the project's README. Every use case is checked against a quote from it.
README
View on GitHubOpfield plugins for DeepSeek Harness
Plugins for DeepSeek Harness (DSH).
| Package | What it does |
|---|---|
@opfield/dsh-mcp-hub |
Every MCP server in one place: eager / lazy / auto tool exposure per server, OAuth for HTTP servers, direct launch of npx packages, and an API for plugins that bring their own servers. Works with any MCP server, not only Opfield. |
@opfield/dsh-opfield |
Opfield instances as MCP servers, models from one instance with an automatic inference token and model sync, plus budget, prompt-cache timer and /compact offer components. Requires MCP Hub. |
@opfield/dsh-multi-repo |
Multi-root workspaces: attach other repositories to a workspace. Attached roots are writable under workspace-write, listed in the model context with their AGENTS.md, and edited from the composer or /roots. Works on its own. |
Install
In DSH open Plugins → Add plugin, enter a spec from the table, then Enable now. Install MCP Hub first: the Opfield plugin needs it. Restart DSH after adding Opfield.
| Plugin | From npm | From this repository |
|---|---|---|
| MCP Hub | @opfield/dsh-mcp-hub |
github:opfield/dsh-plugins#path:/packages/mcp-hub |
| Opfield | @opfield/dsh-opfield |
github:opfield/dsh-plugins#path:/packages/opfield |
| Multi-root workspaces | @opfield/dsh-multi-repo |
github:opfield/dsh-plugins#path:/packages/multi-repo |
To pin a version from the repository, add its tag before path: github:opfield/dsh-plugins#mcp-hub-v0.4.1&path:/packages/mcp-hub, github:opfield/dsh-plugins#opfield-v0.5.2&path:/packages/opfield.
Then open Plugins → Opfield → Add instance, enter the instance address and press Sign in. Each package's README covers the details: MCP Hub, Opfield, Multi-root workspaces.
DSH does not update plugins yet: to upgrade, remove the plugin and add the new version.
Development
npm install # Harness packages the tests run against
npm test
The plugins have no build step. To try a working copy, add it in DSH by absolute path (/path/to/dsh-plugins/packages/mcp-hub).
Release
Bump version in packages/<dir>/package.json, commit, and push a tag <dir>-v<version>, for example mcp-hub-v0.4.1. The Release workflow tests, publishes the package to npm with provenance, and creates a GitHub release.
License
dsh-plugins MCP questions
Can I use the MCP Hub with servers other than Opfield?
Yes, the MCP Hub works with any MCP server.
How do I upgrade a plugin in DSH?
DSH does not currently support automatic plugin updates; you must remove the plugin and add the new version manually.
What does the multi-repo plugin allow me to do?
It enables multi-root workspaces by attaching other repositories to a workspace, allowing them to be writable, listed in model context, and edited via the composer.