DeepSeek Subagent MCP Server
Related Servers
Alternatives to DeepSeek Subagent MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding agents like Claude Code or Codex to delegate tasks to a DeepSeek Harness subagent with its own context window, providing tools for task delegation, result waiting, continuation, and supervision with sandboxed execution.6MIT
- AlicenseNot gradedqualityAmaintenanceExposes DeepSeek as a callable MCP tool, enabling ChatGPT connectors and other MCP clients to invoke it for cross-vendor independent review tasks.1MIT
- AlicenseAqualityCmaintenanceEnables using DeepSeek models as a small, cheap supervised worker from any MCP-compatible client, providing fast flash and deep reasoning tools for bounded tasks.253MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI chat clients to delegate self-contained coding tasks to opencode's free-tier models as a one-shot subagent through a native MCP tool, without requiring shell commands or API keys.MIT
- AlicenseNot gradedqualityBmaintenanceConnects MCP clients to DeepSeek API, including DeepSeek-R1 reasoning with visible chain-of-thought. Provides four tools: generate, chat, reason, and list models.1MIT
- FlicenseAqualityBmaintenanceEnables delegating tasks to a separate, full agentic loop running on a different model, with its own tool access, returning only the final result.4-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusion or overlapping purposes. The tool clearly covers the single action of delegating a sub-task to DeepSeek.
With a single tool, there is no pattern to be inconsistent about. The name 'deepseek_task' is descriptive and follows a clear noun-based naming convention.
One tool is on the thin side; while the server's purpose is narrow, a richer integration might include multiple tools (e.g., different task types or configuration options). The count is borderline but not unreasonable for a single-purpose sub-agent server.
The tool fully covers the stated purpose of delegating a self-contained task and returning the result. Minor gaps exist, such as no way to manage task history or configure multiple output modes, but these are not essential to the core workflow.