DeepSeek Harness Plugin MCP
Related Servers
Alternatives to DeepSeek Harness Plugin MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server bridging ChatGPT to DeepSeek Harness, exposing 13 tools for task submission, status tracking, result retrieval, project/session management, and human-in-the-loop approvals.1MIT
- FlicenseAqualityCmaintenanceMCP server wrapping DeepSeek's agent harness tools into minimal/standard modes, enabling persistent shell, file editing, search, job management, and more via natural language.2-
- AlicenseNot gradedqualityCmaintenanceTurns DeepSeek Harness into an MCP server with tools for session management, agent execution, resources, and OAuth, plus browser automation and GitHub/GitLab integration.67 npm20MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Codex with DeepSeek Harness to delegate coding tasks into isolated worktrees, providing profile-based model routing, single/multi-agent orchestration, and reviewable artifacts.10 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA powerful MCP server that brings the skills.sh ecosystem directly to your AI agents, enabling effortless discovery, installation, and management of skills.1MIT
- FlicenseAqualityCmaintenanceMCP server that lets AI agents drive HMCL (Hello Minecraft! Launcher) programmatically to install Minecraft versions, search/download/import modpacks from Modrinth/CurseForge, and launch/stop the game.131-
TDQS
Scored across 15 tools
Tools are clearly separated into plugin catalog, profile, and runtime operations, but there is slight overlap between list/search and install/runtime_load. Descriptions are detailed enough to resolve ambiguity in most cases.
All tool names follow a consistent snake_case pattern with the dsh_ prefix, using verb phrases like get, list, install, uninstall, start, stop. The only minor deviation is dsh_plugin_status, which is a noun, but overall naming is highly predictable.
15 tools sit at the upper boundary of the ideal range, but each tool maps to a distinct step in the plugin lifecycle (catalog, install, runtime), making the set feel well-scoped and not bloated.
The tool surface covers catalog browsing, plugin installation/removal, and runtime lifecycle management comprehensively. An update operation is missing, but it can be simulated through uninstall/install, so it is not a critical gap.