{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm-next-devtools-mcp","slug":"next-devtools-mcp","name":"next-devtools-mcp","type":"mcp","url":"https://github.com/vercel/next-devtools-mcp#readme","page_url":"https://unfragile.ai/next-devtools-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm-next-devtools-mcp__cap_0","uri":"capability://tool.use.integration.next.js.development.server.introspection.via.mcp.protocol","name":"next.js development server introspection via mcp protocol","description":"Exposes 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.","intents":["Query which routes are currently registered in a Next.js app without parsing the filesystem","Inspect middleware configuration and execution order during development","Check build status and compilation errors from within an AI agent context","Understand server-side rendering vs static generation configuration for specific routes"],"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"],"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":["Next.js 13.0+","Node.js 16+","Active Next.js development server (next dev running)","MCP-compatible client (Claude Desktop, or custom MCP host)"],"input_types":["MCP resource URIs (e.g., 'nextjs://routes', 'nextjs://middleware')","MCP tool invocations with JSON parameters"],"output_types":["JSON-structured route metadata","Middleware configuration objects","Build status reports","Error diagnostics"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_1","uri":"capability://data.processing.analysis.route.and.page.metadata.extraction.from.next.js.app.directory","name":"route and page metadata extraction from next.js app directory","description":"Scans 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.","intents":["Get a complete list of all routes in a Next.js app with their dynamic segment definitions","Understand the layout hierarchy and which layouts apply to which pages","Identify API routes and their HTTP method handlers","Find page components and their file locations for code editing or analysis"],"best_for":["AI agents generating or refactoring Next.js page components","Developers building code generation tools for Next.js","Teams automating documentation of app structure"],"limitations":["Requires filesystem access to the Next.js project directory","Does not execute dynamic route generation logic (getStaticPaths, generateStaticParams) — only reads static file structure","Cannot detect routes defined programmatically outside the app directory convention","Metadata extraction happens at parse time — does not reflect runtime route modifications"],"requires":["Next.js 13+ (app directory support)","Read access to project filesystem","MCP server running in the same environment as the Next.js project"],"input_types":["Filesystem paths to Next.js app directory","MCP resource queries for specific route patterns"],"output_types":["JSON array of route objects with path, segments, and component locations","Nested layout hierarchy trees","API route handler metadata"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_2","uri":"capability://data.processing.analysis.middleware.configuration.and.execution.order.inspection","name":"middleware configuration and execution order inspection","description":"Reads 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.","intents":["Understand which routes are protected by middleware and what conditions apply","Check middleware matcher patterns to see if a new route will be intercepted","Identify custom headers or authentication logic applied by middleware","Debug middleware execution order and conditional routing rules"],"best_for":["AI agents analyzing or generating middleware for authentication, redirects, or request transformation","Teams auditing security middleware configuration","Developers understanding middleware impact on new routes"],"limitations":["Static analysis only — does not execute middleware or evaluate runtime conditions","Cannot detect dynamic matcher patterns generated at runtime","Regex-based matcher extraction may fail for complex or programmatically-generated patterns","Does not track middleware imported from external packages or dynamically loaded modules"],"requires":["middleware.ts or middleware.js file present in Next.js project root","Filesystem read access","MCP server running in project context"],"input_types":["MCP resource request for middleware configuration","Optional route path to check against middleware matchers"],"output_types":["Middleware configuration object with matchers and handlers","Boolean result for route matcher queries","Extracted header and redirect rules"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_3","uri":"capability://automation.workflow.build.status.and.compilation.error.reporting","name":"build status and compilation error reporting","description":"Monitors 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.","intents":["Check if the Next.js app currently has compilation errors before attempting code generation","Get detailed error messages and file locations for build failures","Monitor build progress during development to know when changes are ready","Identify TypeScript type errors that need fixing before running the app"],"best_for":["AI agents that need to verify app buildability before suggesting code changes","Development workflows that require build status checks before deployment","Teams integrating Next.js development into CI/CD-like automation"],"limitations":["Requires active Next.js dev server — cannot report build status for offline projects","Error reporting depends on dev server's internal logging — format may vary across Next.js versions","Does not capture runtime errors or errors that only appear in production builds","Polling-based status checks may have latency — not real-time event streaming"],"requires":["Next.js development server running (next dev)","Access to dev server logs or internal build state APIs","MCP client capable of polling or receiving status updates"],"input_types":["MCP resource request for build status","Optional file path to check for specific errors"],"output_types":["Build status enum (success, building, error)","Array of error objects with file, line, column, and message","Build duration and timestamp metadata"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_4","uri":"capability://data.processing.analysis.server.side.rendering.and.static.generation.configuration.inspection","name":"server-side rendering and static generation configuration inspection","description":"Analyzes 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.","intents":["Determine if a page is server-rendered, statically generated, or dynamically rendered","Check if a page uses incremental static regeneration (ISR) and its revalidation interval","Identify which pages have dynamic segments and how they handle parameter generation","Understand data fetching patterns (server-side props, static props, dynamic data fetching)"],"best_for":["AI agents generating new pages with appropriate rendering modes","Teams auditing rendering configuration for performance optimization","Developers understanding data fetching patterns in existing pages"],"limitations":["Static analysis only — cannot detect rendering mode determined by runtime conditions","Does not execute getStaticPaths or generateStaticParams — cannot enumerate all static routes","Cannot detect rendering mode changes made via middleware or request headers","Regex-based export detection may fail for complex or dynamically-generated exports"],"requires":["Access to page component files (TypeScript or JavaScript)","Filesystem read access","MCP server running in project context"],"input_types":["Page file path or route pattern","MCP resource request for rendering configuration"],"output_types":["Rendering mode enum (ssr, ssg, isr, dynamic)","Revalidation interval for ISR pages","Data fetching function metadata (getServerSideProps, getStaticProps, etc.)","Dynamic segment definitions"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_5","uri":"capability://data.processing.analysis.environment.variable.and.configuration.schema.exposure","name":"environment variable and configuration schema exposure","description":"Reads .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.","intents":["Get a list of available environment variables and their expected types","Check if a required environment variable is configured before generating code that uses it","Understand Next.js configuration settings (image domains, API routes, etc.) when generating features","Verify that generated code references only configured environment variables"],"best_for":["AI agents generating code that depends on environment variables or configuration","Teams ensuring generated code respects project configuration constraints","Developers understanding available configuration options for a Next.js project"],"limitations":["Does not validate environment variable values — only reads names and types","Cannot detect environment variables set via CI/CD systems or runtime environment","next.config.js parsing is limited to static exports — does not execute dynamic configuration","Does not track environment variable usage across the codebase — only reads definitions"],"requires":[".env or .env.local file (optional)","next.config.js file (optional)","Filesystem read access","MCP server running in project context"],"input_types":["MCP resource request for environment variables","MCP resource request for Next.js configuration"],"output_types":["Array of environment variable objects with name and inferred type","Next.js configuration object (images, api, redirects, rewrites, etc.)","Boolean result for environment variable existence checks"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_6","uri":"capability://code.generation.editing.file.system.aware.code.generation.with.path.resolution","name":"file system aware code generation with path resolution","description":"Provides 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.","intents":["Generate a new page component in the correct location within the app directory","Create an API route with proper file naming and HTTP method handling","Generate import statements that correctly reference components and utilities","Validate that a generated file path follows Next.js conventions and won't conflict with existing files"],"best_for":["AI agents generating new Next.js pages, components, and API routes","Code generation tools that need to respect Next.js file structure conventions","Developers using AI to scaffold new features while maintaining project structure"],"limitations":["Does not execute imports or validate that imported modules exist — only checks path syntax","Cannot detect circular dependencies or import conflicts","File generation requires write access to filesystem — MCP server must run with appropriate permissions","Does not automatically update related files (e.g., adding routes to a navigation menu)"],"requires":["Write access to Next.js project filesystem","MCP server running with file system permissions","Understanding of Next.js file conventions in the MCP server"],"input_types":["File path and content for new files","Import statements to validate","File location suggestions based on feature type"],"output_types":["Validated file path","Generated import statements","File creation confirmation","Path conflict warnings"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm-next-devtools-mcp__cap_7","uri":"capability://data.processing.analysis.component.and.utility.discovery.with.usage.analysis","name":"component and utility discovery with usage analysis","description":"Scans 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.","intents":["Find existing components that can be reused instead of generating new ones","Get component prop types and signatures to generate correct usage","Understand utility functions available in the project before generating new ones","Identify design patterns and component composition patterns used in the project"],"best_for":["AI agents generating code that should reuse existing components and utilities","Teams maintaining consistent component usage across a codebase","Developers understanding available component libraries within their project"],"limitations":["Static analysis only — does not execute components or utilities to verify behavior","TypeScript type extraction depends on explicit type annotations — inferred types may be missed","Cannot detect dynamically-imported components or utilities loaded at runtime","Usage analysis may be incomplete for components used in dynamic imports or render functions"],"requires":["Filesystem read access to component and utility files","TypeScript or JSDoc type annotations for accurate type extraction","MCP server running in project context"],"input_types":["MCP resource request for component discovery","Optional search query for component name or type","File path to analyze for component usage"],"output_types":["Array of component objects with name, file path, and prop types","Utility function signatures and descriptions","Usage statistics and locations","Component dependency graph"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":41,"verified":false,"data_access_risk":"high","permissions":["Next.js 13.0+","Node.js 16+","Active Next.js development server (next dev running)","MCP-compatible client (Claude Desktop, or custom MCP host)","Next.js 13+ (app directory support)","Read access to project filesystem","MCP server running in the same environment as the Next.js project","middleware.ts or middleware.js file present in Next.js project root","Filesystem read access","MCP server running in project context"],"failure_modes":["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","Cannot detect routes defined programmatically outside the app directory convention","Metadata extraction happens at parse time — does not reflect runtime route modifications","Static analysis only — does not execute middleware or evaluate runtime conditions","Cannot detect dynamic matcher patterns generated at runtime","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.622703105724606,"quality":0.26,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.902Z","last_scraped_at":"2026-04-22T08:08:13.650Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":64936,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=next-devtools-mcp","compare_url":"https://unfragile.ai/compare?artifact=next-devtools-mcp"}},"signature":"E7Ix0cJ4rSd2SaS94MX4osxtULEjS3zsnUt6cYRvcUdHxA1piho+Xvqr7e+MOK4p8wq19LAi2AeiGssJea0DAQ==","signedAt":"2026-06-23T02:29:25.322Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/next-devtools-mcp","artifact":"https://unfragile.ai/next-devtools-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=next-devtools-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}