deepseek-harness vs mcp-typescript-template
Two of the top projects in Agent and MCP starters, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
deepseek-harness
Plugin-based agent harness from DeepSeek with a local Web UI
mcp-typescript-template
TypeScript starter for remote MCP servers over HTTP with Express and Effect
Verdict
deepseek-harness ranks higher, 70 to 63. Of the 5 score parts we measure for both, deepseek-harness leads on 2, mcp-typescript-template on 1 and 2 are even.
- Adoptiondeepseek-harness leads by 100 points, 100 to 0: a wide gap.
- FreshnessEven at 100.
- Maintenancedeepseek-harness leads by 3 points, 100 to 97: close to even.
- Easy to runmcp-typescript-template leads by 50 points, 50 to 0: a wide gap.
- Agent-readyEven at 85.
Pick deepseek-harness if you are
Developers building agents through plugins, tolerant of breaking changes
- Starts with one npx command; no Docker or database mentioned
- Everything-is-a-plugin design on Cordis, with a dsh-plugin topic for discovery
Pick mcp-typescript-template if you are
Developers starting a remote MCP server in TypeScript
- Example tools cover structured output, annotations and MCP elicitation with accept/decline/cancel handling
- Stateless per-request server following the MCP 2026-07-28 spec, with fallback for older clients
| What we compare | deepseek-harness | mcp-typescript-template |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 100, widely used | 0, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 100, healthy | 97, healthy |
| Easy to run | 0, hard | 50, easy |
| Agent-ready | 85, ready | 85, ready |
| Facts from GitHub and the README | ||
| Stars | 253.9k | 58 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | None published | Oct 2026 |
| Language | TypeScript | TypeScript |
| Docker | No | Yes |
| GPU | Not stated | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
deepseek-harness
DeepSeek Harness (`dsh`) is a TypeScript agent harness built on the Cordis plugin framework, where every component is a plugin. It runs via `npx @deepseek-ai/dsh web` or from a source checkout with pnpm, and serves a Web UI at 127.0.0.1:3080 by default. It is a developer preview, and the README warns of compatibility-breaking changes.
Who it is for: Developers building agents through plugins, tolerant of breaking changes
Strengths
- Starts with one npx command; no Docker or database mentioned
- Everything-is-a-plugin design on Cordis, with a dsh-plugin topic for discovery
- MIT license, documentation site and third-party license notices
- Web UI binds to 127.0.0.1 by default; --no-open skips the browser
Weaknesses
- Developer preview; README warns of compatibility-breaking changes
- No tagged release published
- README does not list supported models, providers or system requirements
- Safety notice must be read before running; its contents are not in the README
- TypeScript
- Needs Node.js, pnpm (source build)
mcp-typescript-template
A degit-able template for building stateless, remote MCP servers on Node 24.11+ using the MCP TypeScript SDK, Express and Effect. It ships two example tools (echo and elicit_echo) with typed input and output schemas, plus an example Agent Skill published through the MCP Skills extension. Build, test, lint and format run through the Vite+ vp CLI.
Who it is for: Developers starting a remote MCP server in TypeScript
Strengths
- Example tools cover structured output, annotations and MCP elicitation with accept/decline/cancel handling
- Stateless per-request server following the MCP 2026-07-28 spec, with fallback for older clients
- Includes Dockerfile, compose file with health check, and in-memory client/server integration tests
- Bundles an example Agent Skill served via skills/list, skills/get and resources/read
Weaknesses
- Requires Node.js 24.11 or newer; Vite+ does not run on earlier Node 24 releases
- Tool code is written in Effect, which adds a learning curve for teams not using it
- HTTP transport only; the README mentions no stdio transport
- No auth or database included; only two toy example tools
- TypeScript
- Needs Node.js 24.11+, Express, Effect, @modelcontextprotocol/server, Vite+
- GitHub template
- Docker
More in Agent and MCP starters
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.