next-devtools-mcp
MCP ServerFreeNext.js development tools MCP server with stdio transport
Capabilities8 decomposed
next.js development server introspection via mcp protocol
Medium confidenceExposes Next.js development server state and metadata through the Model Context Protocol (MCP) using stdio transport, enabling Claude and other MCP clients to query active routes, middleware configuration, build status, and server-side rendering details without direct filesystem access. Implements MCP resource and tool schemas that map to Next.js internal APIs, allowing structured queries about the running development environment.
Bridges Next.js development server internals directly into MCP protocol, allowing AI agents to query live app state without parsing source code or making HTTP requests to the dev server — uses stdio transport for zero-configuration local integration
Unlike generic Next.js API clients or REST-based dev server inspection, this MCP server provides structured, schema-validated access to Next.js metadata through a standardized protocol that Claude and other AI tools natively understand
route and page metadata extraction from next.js app directory
Medium confidenceScans the Next.js app directory structure and extracts metadata about all registered routes, including path patterns, dynamic segments, layouts, and page component locations. Implements directory traversal logic that understands Next.js file conventions (page.tsx, layout.tsx, route.ts) and maps them to runtime route definitions without requiring a full build or server restart.
Implements Next.js file convention parsing (page.tsx, layout.tsx, route.ts patterns) directly in the MCP server, enabling real-time route discovery without requiring a build step or accessing Next.js internal compiler state
More accurate than regex-based route extraction because it understands Next.js file conventions; faster than building and inspecting the Next.js manifest because it reads the filesystem directly
middleware configuration and execution order inspection
Medium confidenceReads and parses the middleware.ts/middleware.js file from a Next.js project and exposes its configuration, matcher patterns, and execution order through MCP resources. Analyzes the middleware code structure to extract route matchers, conditional logic, and any custom headers or redirects defined, allowing AI agents to understand request processing pipelines without executing the middleware.
Parses Next.js middleware.ts as a static artifact and extracts matcher patterns and configuration without executing the middleware code, enabling safe inspection of request processing logic from within an AI agent context
Safer and faster than running middleware in a test environment; more accurate than regex-based route matching because it understands Next.js matcher syntax natively
build status and compilation error reporting
Medium confidenceMonitors the Next.js development server's build state and exposes compilation errors, warnings, and build progress through MCP resources. Queries the dev server's internal build status (via internal APIs or log parsing) and surfaces TypeScript errors, module resolution failures, and other build-time diagnostics in a structured format that AI agents can parse and act upon.
Exposes Next.js dev server build state through MCP, allowing AI agents to query compilation status and errors without parsing console output or making direct HTTP requests to the dev server
More reliable than parsing console logs because it accesses structured build state; more timely than waiting for CI/CD feedback because it reports live dev server status
server-side rendering and static generation configuration inspection
Medium confidenceAnalyzes page and route component files to detect and expose rendering mode configuration (SSR, SSG, ISR, dynamic rendering) through static code analysis. Parses export statements for getServerSideProps, getStaticProps, getStaticPaths, and dynamic() calls, and identifies dynamic segments and searchParams usage to determine rendering behavior without executing the code.
Performs static code analysis on page components to infer rendering mode without executing the code, enabling AI agents to understand data fetching and rendering strategy for code generation and optimization
More accurate than guessing based on file location because it reads actual export statements; faster than building and inspecting the Next.js manifest because it analyzes source code directly
environment variable and configuration schema exposure
Medium confidenceReads .env files, .env.local, and next.config.js from the Next.js project and exposes available environment variables and configuration options through MCP resources. Parses environment variable names and types (inferred from usage or explicit schema) and exposes Next.js configuration settings (image optimization, API routes, redirects, rewrites) in a structured format for AI agents to reference when generating code.
Exposes Next.js project configuration and environment variables through MCP, allowing AI agents to reference project-specific settings when generating code without requiring manual configuration input
More reliable than hardcoding configuration assumptions because it reads actual project files; more complete than environment variable discovery alone because it also exposes next.config.js settings
file system aware code generation with path resolution
Medium confidenceProvides MCP tools that enable AI agents to generate or modify Next.js files with automatic path resolution, import statement generation, and file location validation. Understands Next.js file conventions and directory structure to suggest appropriate file locations for new pages, components, API routes, and middleware, and validates that generated imports will resolve correctly within the project structure.
Integrates Next.js file convention understanding directly into MCP tools, enabling AI agents to generate files in correct locations and with proper import paths without manual path specification
More accurate than generic file generation because it understands Next.js-specific conventions; more reliable than AI-generated paths because it validates against actual project structure
component and utility discovery with usage analysis
Medium confidenceScans the Next.js project for reusable components, utilities, and hooks, and exposes their signatures, prop types, and usage patterns through MCP resources. Performs static analysis on component files to extract TypeScript/JSDoc type information, identifies commonly-used utilities, and tracks which components are used where, enabling AI agents to reference existing code when generating new features.
Performs static analysis on Next.js components to extract type information and usage patterns, enabling AI agents to discover and reuse existing components without manual documentation or imports
More accurate than searching for components by name because it analyzes actual type signatures; more complete than component documentation because it discovers components automatically
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with next-devtools-mcp, ranked by overlap. Discovered automatically through the match graph.
next-devtools-mcp
Next.js development tools MCP server with stdio transport
xmcp
The TypeScript MCP framework
@modelcontextprotocol/server-basic-svelte
Basic MCP App Server example using Svelte
Open-Sourced MCP Servers Directory
** - A curated list of MCP servers by **[mcpso](https://mcp.so)**
@modelcontextprotocol/express
Express adapters for the Model Context Protocol TypeScript server SDK - Express middleware
Next.js MCP Server Template
** (Typescript) - A starter Next.js project that uses the MCP Adapter to allow MCP clients to connect and access resources.
Best For
- ✓AI agents and Claude instances debugging Next.js applications
- ✓Teams building AI-assisted development workflows for Next.js
- ✓Developers integrating Next.js introspection into MCP-compatible tools
- ✓AI agents generating or refactoring Next.js page components
- ✓Developers building code generation tools for Next.js
- ✓Teams automating documentation of app structure
- ✓AI agents analyzing or generating middleware for authentication, redirects, or request transformation
- ✓Teams auditing security middleware configuration
Known Limitations
- ⚠Requires active Next.js development server running on the same machine
- ⚠Only exposes metadata available through Next.js public APIs; internal compiler state may be inaccessible
- ⚠stdio transport limits concurrent connections — single client at a time
- ⚠No built-in caching of server state — each query hits the live dev server
- ⚠Requires filesystem access to the Next.js project directory
- ⚠Does not execute dynamic route generation logic (getStaticPaths, generateStaticParams) — only reads static file structure
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
Repository Details
Package Details
About
Next.js development tools MCP server with stdio transport
Categories
Alternatives to next-devtools-mcp
Are you the builder of next-devtools-mcp?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →