mcp-use vs mcp-for-next.js
Two of the top projects in MCP servers and chat-host apps, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
mcp-use
TypeScript framework for building MCP servers with React Views and an Inspector
mcp-for-next.js
Stateless MCP server route for a Next.js App Router app
Verdict
mcp-use ranks higher, 56 to 39. Of the 5 score parts we measure for both, mcp-use leads on 2, mcp-for-next.js on none and 3 are even.
- Adoptionmcp-use leads by 32 points, 68 to 36: a wide gap.
- FreshnessEven at 100.
- Maintenancemcp-use leads by 50 points, 94 to 44: a wide gap.
- Easy to runEven at 0.
- Agent-readyEven at 0.
Pick mcp-use if you are
TypeScript developers building MCP servers and ChatGPT or Claude apps
- Zod schemas flow from tool input and output into React View props
- Inspector served at /mcp/inspector in dev; headless CLI can call tools and screenshot Views
Pick mcp-for-next.js if you are
Next.js teams exposing tools to MCP clients
- Stateless Streamable HTTP; no Redis or session store required
- Current 2026-07-28 protocol plus 2025 Streamable HTTP compatibility
| What we compare | mcp-use | mcp-for-next.js |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 68, popular | 36, known |
| Freshness | 100, active | 100, active |
| Maintenance | 94, healthy | 44, patchy |
| Easy to run | 0, hard | 0, hard |
| Agent-ready | 0, none | 0, none |
| Facts from GitHub and the README | ||
| Stars | 10.8k | 373 |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Jul 2026 |
| Last release | Oct 2026 | None published |
| Language | TypeScript | JavaScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
mcp-use
mcp-use is a TypeScript v2 framework, built on the official MCP TypeScript SDK, for writing MCP servers with Zod-typed tools. It binds React Views to tools so they render as interactive apps in hosts such as ChatGPT and Claude. It ships a dev Inspector, a headless client CLI, a View screenshot command, tunneling, and a deploy command targeting Manufact.
Who it is for: TypeScript developers building MCP servers and ChatGPT or Claude apps
Strengths
- Zod schemas flow from tool input and output into React View props
- Inspector served at /mcp/inspector in dev; headless CLI can call tools and screenshot Views
- Built-in tunnel (mcp-use dev --tunnel) for testing in ChatGPT and Claude before deploy
- MIT licensed, with a self-hosting guide alongside the hosted option
Weaknesses
- v2 is a breaking change from v1; a migration guide is needed
- Benchmark and comparison figures are the project's own, not independent
- One-command npm run deploy targets the vendor's Manufact platform
- Example apps live in separate repos, not in the main package
- TypeScript
- Needs Node.js, npm, React, Zod
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
More in MCP servers and chat-host apps
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.