mcp-server-skills

Build MCP servers in Next.js by defining shared Zod schemas in a central lib/ folder, then reference them in both your route.ts handlers and server actions. This single source of truth eliminates duplication and ensures consistent validation across HTTP, SSE, and other transports.

Yes. MCP handlers work with Next.js server actions by sharing Zod-validated tool definitions. Define your actions in app/actions/ and wire them to your MCP routes through a shared schema registry, enabling reusable logic across transports.

Set up multi-transport MCP endpoints by implementing a single MCP registry and routing it through app/api/[transport]/route.ts. This pattern handles HTTP, SSE, and other protocols with minimal route wiring and centralized server logic.

No. Use a dynamic route parameter [transport] in app/api/[transport]/route.ts to handle multiple MCP protocols with one handler. Route all transports through a unified MCP registry defined in your shared lib/ schema files.

Zod schemas serve as both validation and documentation for MCP tool definitions. Define them once in lib/ and import them in routes and actions, eliminating duplicate type definitions and ensuring input validation consistency across your MCP endpoints.

Bootstrap with frontmatter-driven identity in SKILL.md, implement app/api/[transport]/route.ts for transport handling, create app/actions/ for server logic, and centralize tool schemas in lib/. This structure provides a complete multi-transport MCP foundation.