@vercel/mcp-adapter

What is @vercel/mcp-adapter?

@vercel/mcp-adapter is a Vercel adapter for the Model Context Protocol (MCP) that enables real‑time communication between applications and AI models. It supports Next.js (13+) and Nuxt (3+) frameworks and provides both Streamable HTTP and Server‑Sent Events transports.

How to use @vercel/mcp-adapter?

Install the package along with @modelcontextprotocol/[email protected] and zod. Create a handler in a Next.js API route (e.g. app/api/[transport]/route.ts) using createMcpHandler, register tools with Zod input schemas, and export the handler as GET and POST. Clients can connect directly via Streamable HTTP or through mcp-remote for stdio‑only clients.

Key features of @vercel/mcp-adapter

• Supports Next.js and Nuxt frameworks
• Streamable HTTP and Server-Sent Events transports
• Optional Redis integration for SSE transport resumability
• Full TypeScript type definitions included
• Enables dynamic routing and tool registration

Use cases of @vercel/mcp-adapter

• Deploy an MCP server on Vercel for AI tool integration
• Build real‑time, AI‑powered applications with custom tools
• Connect with Claude Desktop, Cursor, or Windsurf via MCP
• Use SSE for long‑lived connections with optional Redis persistence

FAQ from @vercel/mcp-adapter

What runtime dependencies are required?

Next.js 13+ or Nuxt 3+, Node.js 18+, and optionally Redis for SSE resumability.

Why should I use @modelcontextprotocol/sdk version 1.26.0 or later?

Versions prior to 1.26.0 contain a security vulnerability. Always use at least 1.26.0.

How do I connect clients that only support stdio?

Use mcp-remote (available on npm) to bridge HTTP to stdio. Configure it as a command in your MCP client settings.

Does the adapter support authentication?

Yes. The documentation includes separate guides for OAuth and token verification.

Can I use this adapter with Nuxt?

Yes. The adapter supports Nuxt 3+ and provides examples in the advanced usage documentation.