Introduction

The philosophy of DeepSeek Harness is that “everything is a plugin.” When multiple MCP servers are integrated into Harness, each server exposes its tool Schema to the model, causing linear growth in context usage. neoxider-mcp-hub was created to solve this problem.

What It Is

neoxider-mcp-hub is an integration plugin maintained by NeoXider and licensed under the MIT License. It is a “lazy loading” capability proxy that consolidates all of your MCP Schemas into a single resident tool.

The core value of the plugin is: while maintaining unchanged tool selection accuracy, it reduces resident context usage by 93.2%. This saving has been measured, not estimated.

Core Features

The plugin mainly provides the following capabilities:

  • MCP and Skill Proxy: Consolidates multiple MCP servers and skills into a single resident tool named capability_hub. The host only needs to interact with this one tool.
  • Lazy Loading: The proxy checks permissions, wakes up a trusted server on demand, executes the operation, and then closes it, without requiring it to remain resident.
  • Token Optimization: By inlining a capability catalog in the tool description, it avoids sending Schemas repeatedly for each tool, thereby saving tokens.
  • Skill Support: Supports on-demand loading of skill bodies.

Installation and Enablement

There is currently no officially provided direct installation command. You need to integrate the plugin into Harness via source code or directory.

Before configuration, ensure that package.json defines the necessary file structure (such as dist/src, data/catalog.json, etc.) and the dsh configuration block. The plugin runs under the current DSH process permissions; inspect the source code and license before installation.

Typical Usage

After enabling the plugin in the DSH configuration, the model no longer faces dozens of tool Schemas, but instead faces a single capability_hub. When invoking it, you need to construct a specific JSON action:

{
  "action": "tools",
  "name": "playwright",
  "query": "click"
}

Internally, the plugin parses this request, looks up the catalog, wakes up the corresponding server, and executes the operation.

Applicable Scenarios and Cautions

This plugin is not free and is not suitable for all scenarios:

  • Applicable Scenario: When you have many MCP servers but each task uses only a few of them, using the proxy can save a large amount of resident context.
  • Non-Applicable Scenario: If every task requires using all configured tools, static configuration (classic mode) is actually cheaper.
  • Cost Model: Classic mode is a one-time payment, while proxy mode is an on-demand payment at runtime. In the JSON example above, direct calls to tools are the most economical path.

The plugin uses catalog retrieval to decide which capability to call, so the quality of the catalog descriptions directly affects the model’s selection accuracy.

Conclusion

neoxider-mcp-hub provides a mechanism for on-demand capability loading in DeepSeek Harness, with measured data demonstrating its ability to save context in multi-server environments.

Plugin Catalog | GitHub Repository