What is MCP in DeepSeek Harness?

Model Context Protocol is a standard interface for exposing tools and data to a model. DSH reaches MCP servers through an MCP client.

Do I need a plugin to use MCP with DSH?

You need an MCP client path. Plugins in this category provide or extend it.

Is an MCP server the same as a DSH plugin?

No. An MCP server is a separate process speaking a standard protocol; a DSH plugin loads into the harness itself.

MCP plugins

DSH MCP plugins connect DeepSeek Harness to the Model Context Protocol — running or consuming MCP servers so tools built for the wider MCP ecosystem become available inside DSH.

62 cataloged

Cataloged projects

Repositories with traceable evidence of a DeepSeek Harness relationship. They have not been reviewed, install tested, or security checked — the signal below each one is the whole of what the registry currently knows.

How cataloging works

dsh-mcp-center

drfccv

Cataloged

Connect any MCP server to your DeepSeek Harness — point, click, done.

README documents a DSH install command Package metadata declares a DSH dependency

1TypeScriptMITRun a check

LiuHe

wulun811

Cataloged

LLM-native code toolkit: Rust multi-language parser (tree-sitter) + 44 MCP tools for atomic editing, impact analysis, reference tracing and deterministic zero-LLM code quality gates. Built for the handless, eyeless, memoryless LLM.

README documents a DSH install command

1JavaScriptMITRun a check

MCP plugins: common questions

What is MCP in DeepSeek Harness?: Model Context Protocol is a standard interface for exposing tools and data to a model. DSH reaches MCP servers through an MCP client.
Do I need a plugin to use MCP with DSH?: You need an MCP client path. Plugins in this category provide or extend it.
Is an MCP server the same as a DSH plugin?: No. An MCP server is a separate process speaking a standard protocol; a DSH plugin loads into the harness itself.