MCP with Next.js (Vercel)

Dependency freshness

Declared = lowest version the kit's dependency file (package.json, pyproject.toml or requirements.txt) allows. Latest = the npm "latest" tag or the newest PyPI release. TypeScript, the Stripe SDK, FastAPI and other 0.x packages are shown but not counted in the verdict.

What's in the stack

Framework

Next.js

Detected from declared dependencies. A listed package means it's installed, not necessarily fully wired up.

What the README says you get

• API
  Stateless MCP serveradd a stateless MCP server to a Next.js App Router application
• API
  MCP TypeScript SDK v2uses `mcp-handler` 2 and the MCP TypeScript SDK v2
• API
  Native 2026-07-28 protocolThe current 2026-07-28 MCP protocol is served natively
• API
  Streamable HTTP compatibilityStateless clients using 2025-era Streamable HTTP are supported by the compatibility layer
• API
  Custom tools, prompts, resourcesUpdate `app/mcp/route.ts` with your tools, prompts, and resources
• Deploy
  Node.js 20+Requires Node.js 20 or later
• Deploy
  Fluid computeMake sure you have Fluid compute enabled for efficient execution
• Testing
  Sample MCP client`scripts/test-client.mjs` connects over Streamable HTTP, lists the available tools, and calls `echo`

Extracted from the kit's README by a local AI model (deepseek-flash) on Sep 29, 2026. Every item is checked against an exact README quote; 1 unverifiable item was discarded. A README claim is the maker's description, not something we tested.