"Next.js" matching MCP servers:

Provides AI agents with access to a comprehensive database of 200+ Next.js documentation URLs for intelligent document selection and retrieval. Enables Claude and other AI assistants to analyze user queries and recommend the most relevant Next.js documentation pages.

A sample MCP server implementation for Next.js projects that uses the Vercel MCP Adapter to handle protocol requests across different transport methods.

A template MCP server built with Next.js using the Vercel MCP Adapter. Provides a framework for deploying MCP servers with custom tools, prompts, and resources on Vercel with SSE transport support.

A sample implementation of a Model Context Protocol server using Next.js and the Vercel MCP Adapter, allowing developers to create AI assistants with custom tools and resources.

A template for deploying Model Context Protocol servers as Next.js routes using the mcp-handler adapter, enabling easy integration of MCP tools, prompts, and resources into any Next.js application.

A Next.js MCP server template using mcp-handler 2 and the MCP TypeScript SDK v2, providing a stateless MCP server for App Router applications with built-in support for the 2026-07-28 protocol and compatibility with 2025-era Streamable HTTP clients.

Enables secure MCP server functionality with Clerk authentication and user-specific API key management. Provides Next.js documentation tools through protected endpoints with multiple authentication methods including OAuth 2.1 with PKCE.

A sample implementation of Model Context Protocol server using Next.js and the Vercel MCP Adapter, allowing developers to create custom AI agent backends with tools, prompts, and resources.

A drop-in MCP server implementation for Next.js projects using Vercel MCP Adapter, allowing developers to integrate model context protocol functionality with custom tools, prompts, and resources.

A template for building MCP servers in Next.js applications using the Vercel MCP Adapter. Provides a foundation for adding custom tools, prompts, and resources to any Next.js project with deployment support on Vercel.

Provides a template to run an MCP server in a Next.js project using the Vercel MCP Adapter, with SSE transport supported via Redis.

Provides comprehensive documentation search for Next.js 15+ and Tailwind CSS 3+, along with 27 production-ready Catalyst UI components and 13 design patterns for building modern web applications.

Analyzes GitHub repositories and provides advanced optimization recommendations for Next.js and React projects, covering clean architecture, SOLID principles, performance patterns, and best practices.

A minimal MCP server demonstrating how to build ChatGPT-compatible applications using Next.js with widget rendering capabilities. Provides a starter template for integrating Next.js applications with the ChatGPT Apps SDK through the Model Context Protocol.

A minimal starter for building OpenAI Apps SDK compatible MCP servers that support native widget rendering within ChatGPT. It demonstrates how to integrate Next.js tools and resources into the ChatGPT interface using the Model Context Protocol.

Enables AI coding agents to audit websites for PHP runtime vulnerabilities, compile a live Zero-PHP Next.js App Router replacement preview from a WordPress/PHP site, and retrieve remediation guidance.

Combines Midnight Network blockchain development tools with Next.js DevTools for building decentralized applications, supporting contract development, wallet management, and Next.js diagnostics.

A basic MCP server implementing a weather tool using Next.js and the Vercel MCP adapter.

Next.js-based MCP server using mcp-handler for Vercel deployment, supporting SSE transport and Redis integration.

Publishes a stateless MCP endpoint on a Next.js App Router route that speaks Streamable HTTP and runs on any serverless host, exposing example tools (add, get_time, whoami) that clients like Claude Code, Cursor, and MCP Inspector can call. A loopback client forwards per-request context, such as a caller id or a user-supplied API key, in a header so tools can act for that one request without storing anything.