mcp-typescript-template vs mcp-for-next.js
Two of the top mcp servers and chat-host apps, side by side: score, setup, license, activity and what each review found.
mcp-typescript-template
Express and Effect template for a stateless remote MCP server
mcp-for-next.js
Stateless MCP server route for a Next.js App Router app
| What we compare | mcp-typescript-template | mcp-for-next.js |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 0, niche | 47, known |
| Freshness | 100, active | 100, active |
| Maintenance | 99, healthy | 44, patchy |
| Easy to run | 50, easy | 0, hard |
| Agent-ready | 85, ready | 0, none |
| Facts from GitHub and the README | ||
| Stars | 58 | 373 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Jul 2026 |
| Last release | Sep 2026 | None published |
| Language | TypeScript | JavaScript |
| Docker | Yes | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
mcp-typescript-template
TypeScript 7 project serving a stateless MCP endpoint at /mcp on port 3000 via Express and createMcpHandler from the MCP TypeScript SDK, with Effect for config, logging and errors. Ships echo and elicit_echo tools with outputSchema, structuredContent and annotations, HTTP-boundary and in-memory tests, a Dockerfile and compose with a /health check. For TypeScript teams starting a remote MCP server; no auth.
Who it is for: TypeScript developers building a remote MCP server
Strengths
- Stateless per the 2026-07-28 spec with SDK fallback for older clients
- Tests at the HTTP boundary and against an in-memory client
- Typed tool I/O via Effect Schema adapted to MCP Standard Schema
- Dockerfile and docker-compose with health check
Weaknesses
- No auth or OAuth; remote hosts will need it
- Effect is a hard dependency with a learning curve
- TypeScript 7 compiler plus a TS6 alias for ESLint is unusual tooling
- TypeScript, MCP TypeScript SDK (@modelcontextprotocol/server)
- GitHub template
- Docker
mcp-for-next.js
Next.js App Router project where app/mcp/route.ts hosts a stateless MCP server through mcp-handler 2 and the MCP TypeScript SDK v2, serving the 2026-07-28 protocol natively with a compatibility layer for 2025-era Streamable HTTP clients. Includes a sample client script that lists tools and calls echo. For teams adding an MCP endpoint to an existing Next.js app on Vercel; no auth is wired.
Who it is for: Next.js teams exposing tools to MCP clients
Strengths
- Stateless Streamable HTTP; no Redis or session store required
- Current 2026-07-28 protocol plus 2025 Streamable HTTP compatibility
- Sample client script for smoke-testing the endpoint
Weaknesses
- No auth; remote MCP clients will need OAuth added
- Deprecated HTTP+SSE transport is not supported
- Only an echo tool; the README is a few lines
- No tests or Docker
- JavaScript, MCP TypeScript SDK v2, mcp-handler 2