Next.js DevTools MCP
OfficialRelated Servers
Alternatives to Next.js DevTools MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides current Next.js 16 documentation to AI assistants, enabling version-accurate lookups, code generation, and configuration guidance for App Router, Pages Router, Server Components, and Tailwind CSS v4.5 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to automate Next.js development including project scaffolding, React component generation, API route creation, and full-stack application workflows with TypeScript and Tailwind CSS support.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to inspect Next.js codebases, analyze App Router and Pages Router structure, discover API routes, and audit build performance through controlled tools.4 npmMIT
- AlicenseAqualityDmaintenanceProvides 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.111 npm13MIT
- AlicenseBqualityDmaintenanceMonitors Next.js development servers with intelligent error categorization, smart diagnostics, and performance tracking.8MIT
- FlicenseNot gradedqualityDmaintenanceAutomatically generates typed React hooks for Next.js projects by crawling API routes, GraphQL queries, and components. Analyzes pages to suggest optimal render modes (SSR/CSR/ISR) and produces comprehensive documentation with AI-powered guidance.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: browser automation via CLI, executing MCP tools on the dev server, accessing local documentation, and discovering running servers and tools. There is no overlap or ambiguity.
Tools use a consistent snake_case convention. Three tools share the 'nextjs_' prefix, while 'browser_eval' deviates slightly but still follows the same pattern. The naming is predictable and readable.
With 4 tools, the set is well-scoped for a Next.js DevTools MCP server. Each tool covers a necessary aspect: discovery, execution, documentation access, and browser automation. No redundant or missing tools.
The tool surface covers the primary needs for interacting with a Next.js development environment: discovering server state, executing diagnostics, accessing version-accurate docs, and automating browser testing. There are no obvious gaps.