mcp-typescript-template vs eve-software-factory-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.
mcp-typescript-template
TypeScript starter for remote MCP servers over HTTP with Express and Effect
eve-software-factory-template
eve pipeline that turns GitHub or Linear issues into reviewed draft PRs
Verdict
mcp-typescript-template ranks higher, 63 to 59. Of the 5 score parts we measure for both, mcp-typescript-template leads on 2, eve-software-factory-template on 2 and 1 is even.
- Adoptioneve-software-factory-template leads by 30 points, 30 to 0: a wide gap.
- FreshnessEven at 100.
- Maintenancemcp-typescript-template leads by 62 points, 97 to 35: a wide gap.
- Easy to runeve-software-factory-template leads by 17 points, 67 to 50: a wide gap.
- Agent-readymcp-typescript-template leads by 15 points, 85 to 70: a wide gap.
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
Pick eve-software-factory-template if you are
Teams piloting agent-written pull requests with human merge
- Reviewer is isolated from the implementer; verdicts are made against the real diff
- Six entry points including red-CI self-repair on factory branches only
| What we compare | mcp-typescript-template | eve-software-factory-template |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 0, niche | 30, known |
| Freshness | 100, active | 100, active |
| Maintenance | 97, healthy | 35, patchy |
| Easy to run | 50, easy | 67, easy |
| Agent-ready | 85, ready | 70, partly |
| Facts from GitHub and the README | ||
| Stars | 58 | 1.2k |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Sep 2026 |
| Last release | Oct 2026 | None published |
| Language | TypeScript | TypeScript |
| Docker | Yes | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
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
eve-software-factory-template
An eve pipeline named Foreman: label an issue factory, @mention it, or delegate from Linear, and four agents (classifier, analyst, implementer, reviewer) each run in their own sandbox and end with a draft pull request on FACTORY_REPO. The reviewer sees only the pushed branch, a factory brain keeps notes about your repo between runs, and it deploys to Vercel with GitHub and Linear connectors. For teams piloting agent-written PRs with human merge.
Who it is for: Teams piloting agent-written pull requests with human merge
Strengths
- Reviewer is isolated from the implementer; verdicts are made against the real diff
- Six entry points including red-CI self-repair on factory branches only
- Local dev TUI treats runs as untrusted; GitHub writes wait for approval
- Separate docs site; CLAUDE.md and AGENTS.md included
Weaknesses
- Tied to eve, Vercel Connect, Vercel Sandbox and Vercel Blob
- No model provider named in the README; model access comes through the Vercel stack
- No tests listed
- First task fails if the GitHub App cannot reach FACTORY_REPO; the error surfaces late
- TypeScript, eve, ai-sdk
- Needs vercel, github-app-connector, linear-connector, vercel-blob
- GitHub template
- env example file
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.