{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-next-devtools-mcp","slug":"npm-next-devtools-mcp","name":"next-devtools-mcp","type":"mcp","url":"https://www.npmjs.com/package/next-devtools-mcp","page_url":"https://unfragile.ai/npm-next-devtools-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-next-devtools-mcp__cap_0","uri":"capability://tool.use.integration.next.js.project.introspection.via.mcp.protocol","name":"next.js project introspection via mcp protocol","description":"Exposes Next.js project metadata and configuration through the Model Context Protocol (MCP) using stdio transport, allowing Claude and other MCP-compatible clients to query project structure, routes, pages, and configuration without direct filesystem access. Implements MCP resource and tool schemas to standardize how LLMs interact with Next.js-specific project information.","intents":["Query Next.js project structure and routing configuration from Claude","Retrieve page and component metadata for code generation context","Inspect Next.js configuration (next.config.js) programmatically via MCP","Enable Claude to understand project layout before suggesting code changes"],"best_for":["AI-assisted Next.js development workflows using Claude","Teams building LLM agents that need to understand Next.js projects","Developers using Claude Desktop or MCP-compatible IDEs"],"limitations":["Requires MCP client support — not compatible with REST APIs or direct SDK usage","Limited to stdio transport — no network/HTTP transport option","Project introspection is read-only; cannot modify configuration via MCP","Depends on Next.js project being properly initialized with valid configuration"],"requires":["Node.js 16+","Next.js 12+ project","MCP-compatible client (Claude Desktop, Cline, etc.)","stdio transport capability in client environment"],"input_types":["MCP resource requests (JSON-RPC)","MCP tool invocations (JSON-RPC)"],"output_types":["JSON project metadata","Route definitions","Configuration objects","File structure representations"],"categories":["tool-use-integration","mcp-server"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_1","uri":"capability://tool.use.integration.next.js.route.and.page.discovery","name":"next.js route and page discovery","description":"Automatically discovers and catalogs all Next.js routes (App Router and Pages Router), page components, API routes, and middleware through AST parsing and filesystem scanning. Exposes discovered routes as MCP resources with metadata including route parameters, HTTP methods, and component locations, enabling LLMs to understand the complete routing topology without manual configuration.","intents":["Get a complete list of all routes in a Next.js project","Understand route parameter patterns and dynamic segments","Identify which API routes exist and their HTTP methods","Locate page components and their file paths for context injection"],"best_for":["LLM-assisted code generation for new pages or API routes","AI agents that need to understand existing routing before suggesting changes","Developers using Claude to refactor or extend Next.js applications"],"limitations":["Route discovery may miss dynamically-generated routes created at runtime","Requires filesystem access to scan project directories","No support for routes defined outside standard Next.js directories","Middleware discovery limited to next.config.js and middleware.ts/js files"],"requires":["Next.js 12+ with either App Router or Pages Router","Readable filesystem access to project root","Valid next.config.js or default Next.js configuration"],"input_types":["MCP resource request for routes","MCP tool invocation with optional filters"],"output_types":["JSON array of route objects","Route metadata (path, methods, parameters)","Component file paths and locations"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_2","uri":"capability://automation.workflow.development.server.lifecycle.management.via.mcp","name":"development server lifecycle management via mcp","description":"Provides MCP tools to start, stop, and monitor the Next.js development server (next dev) as a subprocess, with stdio/stderr capture and process state tracking. Enables LLM clients to control the dev server lifecycle without direct shell access, integrating server status into the MCP context for real-time feedback on compilation and runtime errors.","intents":["Start the Next.js dev server from Claude without manual terminal commands","Stop or restart the dev server when needed for configuration changes","Monitor dev server logs and compilation errors in real-time","Detect when the dev server is ready to accept requests"],"best_for":["Automated Next.js development workflows in Claude Desktop","LLM agents that need to test code changes by running the dev server","Developers using Claude to iterate on Next.js projects with live feedback"],"limitations":["Subprocess management adds complexity — requires proper cleanup on client disconnect","Dev server output (stdout/stderr) may be voluminous; requires filtering/buffering","No built-in support for custom dev server configurations (port, hostname)","Process termination may not be graceful if client crashes without cleanup"],"requires":["Node.js 16+","Next.js 12+ project with valid package.json","npm or yarn installed and available in PATH","Sufficient system resources to run dev server alongside MCP server"],"input_types":["MCP tool invocation (start, stop, status)","Optional configuration parameters (port, hostname)"],"output_types":["Process status (running, stopped, error)","Dev server logs and error messages","Ready state confirmation"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_3","uri":"capability://memory.knowledge.file.based.context.injection.for.code.generation","name":"file-based context injection for code generation","description":"Implements MCP resources that expose Next.js project files (pages, components, API routes, config) as readable context that Claude can request on-demand. Uses lazy-loading and caching to avoid overwhelming context windows, with support for filtering by file type, directory, or pattern to provide targeted code context for generation tasks.","intents":["Provide Claude with existing component code as reference for new components","Share API route examples to maintain consistency in new endpoints","Expose configuration files (next.config.js, tsconfig.json) for context","Allow Claude to read related files before suggesting changes"],"best_for":["Code generation workflows where Claude needs to match existing patterns","Refactoring tasks that require understanding current implementation","Teams with style guides or architectural patterns in code"],"limitations":["Large files or many files can exceed Claude's context window","No built-in syntax highlighting or code formatting in MCP response","Binary files or non-text files cannot be exposed via MCP","File changes during MCP session may not be reflected without cache invalidation"],"requires":["Readable filesystem access to project files","Next.js project with TypeScript or JavaScript files","MCP client with sufficient context window for file contents"],"input_types":["MCP resource request with file path or pattern","Optional filters (file type, directory, size limits)"],"output_types":["File contents as text","File metadata (size, type, modification time)","Directory listings with file metadata"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_4","uri":"capability://memory.knowledge.typescript.javascript.type.information.exposure","name":"typescript/javascript type information exposure","description":"Extracts and exposes TypeScript type definitions, interfaces, and type information from the Next.js project through MCP resources, enabling Claude to understand component props, API response types, and function signatures. Uses TypeScript compiler API or similar to parse type annotations and generate type documentation accessible via MCP.","intents":["Understand component prop types before generating new components","Know API response types when generating API route handlers","Access type definitions for shared utilities and helpers","Generate type-safe code that matches existing type contracts"],"best_for":["TypeScript-based Next.js projects with strict type checking","Teams that want Claude to generate type-safe code","Projects with complex type hierarchies or generic types"],"limitations":["Requires TypeScript to be installed and configured in project","Complex generic types may be difficult to represent in text format","Type inference may be incomplete without full project compilation","No support for runtime type information or reflection"],"requires":["TypeScript 4.0+ installed in project","Valid tsconfig.json with proper configuration","Next.js project with .ts or .tsx files"],"input_types":["MCP resource request for type information","Optional file path or symbol name"],"output_types":["Type definitions in text format","Interface and type alias documentation","Function signature information"],"categories":["memory-knowledge","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_5","uri":"capability://tool.use.integration.environment.variable.and.secrets.management.interface","name":"environment variable and secrets management interface","description":"Provides MCP tools to read and validate environment variables from .env, .env.local, and .env.production files without exposing sensitive values directly. Implements safe access patterns that allow Claude to understand what environment variables are available and their expected types/formats while preventing accidental exposure of secrets in conversation logs.","intents":["Understand what environment variables are available in the project","Know which variables are required for API routes or components","Generate code that correctly references environment variables","Validate that required environment variables are configured"],"best_for":["Projects with environment-dependent configuration","Teams that want Claude to generate code using correct env var names","Security-conscious teams that need to prevent secret exposure"],"limitations":["Cannot expose actual secret values to Claude (by design)","Requires .env files to be readable by MCP server process","No support for runtime environment variable injection","May not detect environment variables set via system environment"],"requires":[".env or .env.local file in project root","Readable filesystem access to env files","Next.js project with environment variable usage"],"input_types":["MCP tool invocation to list env variables","Optional filter for variable names or patterns"],"output_types":["List of available environment variable names","Variable metadata (required, type, description)","Validation results (missing, invalid format)"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_6","uri":"capability://automation.workflow.build.and.compilation.error.reporting","name":"build and compilation error reporting","description":"Captures and exposes Next.js build errors, TypeScript compilation errors, and ESLint warnings through MCP resources, providing structured error information including file paths, line numbers, error messages, and suggested fixes. Integrates with the dev server to report errors in real-time as code changes are made.","intents":["Get detailed error information when code generation produces invalid code","Understand TypeScript compilation errors in generated components","Access ESLint warnings to improve code quality","Provide error context to Claude for iterative code fixes"],"best_for":["Iterative code generation workflows where Claude needs error feedback","Projects with strict TypeScript or ESLint configurations","Teams that want Claude to self-correct based on build errors"],"limitations":["Error reporting depends on dev server being active","Some errors may only appear during full build, not in dev mode","Error messages may be verbose or unclear without additional context","No built-in error deduplication or grouping"],"requires":["Next.js dev server running","TypeScript or JavaScript project","Optional: ESLint configuration for linting errors"],"input_types":["MCP resource request for current errors","Optional file path filter"],"output_types":["Structured error objects with file, line, column, message","Error severity (error, warning)","Suggested fixes or related documentation"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-next-devtools-mcp__cap_7","uri":"capability://data.processing.analysis.performance.metrics.and.bundle.analysis","name":"performance metrics and bundle analysis","description":"Exposes Next.js performance metrics (build time, bundle size, page load metrics) and provides MCP tools to analyze bundle composition, identify large dependencies, and track performance regressions. Integrates with Next.js built-in analytics and optional tools like Bundle Analyzer to provide actionable performance insights.","intents":["Understand current bundle size and identify optimization opportunities","Track performance impact of code changes","Identify large dependencies that could be replaced or removed","Generate performance-optimized code that avoids unnecessary imports"],"best_for":["Performance-critical Next.js applications","Teams that want Claude to generate bundle-size-aware code","Projects with strict performance budgets"],"limitations":["Requires build to complete for accurate metrics","Bundle analysis may be slow for large projects","Performance metrics vary based on build configuration and environment","No real-time performance monitoring during development"],"requires":["Next.js 12+ with build analytics enabled","Optional: @next/bundle-analyzer or similar tool","Sufficient disk space for build artifacts"],"input_types":["MCP tool invocation to analyze bundle","Optional filters for specific pages or routes"],"output_types":["Bundle size metrics (total, per-page, per-dependency)","Dependency analysis (size, count, duplicates)","Performance recommendations"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+","Next.js 12+ project","MCP-compatible client (Claude Desktop, Cline, etc.)","stdio transport capability in client environment","Next.js 12+ with either App Router or Pages Router","Readable filesystem access to project root","Valid next.config.js or default Next.js configuration","Next.js 12+ project with valid package.json","npm or yarn installed and available in PATH","Sufficient system resources to run dev server alongside MCP server"],"failure_modes":["Requires MCP client support — not compatible with REST APIs or direct SDK usage","Limited to stdio transport — no network/HTTP transport option","Project introspection is read-only; cannot modify configuration via MCP","Depends on Next.js project being properly initialized with valid configuration","Route discovery may miss dynamically-generated routes created at runtime","Requires filesystem access to scan project directories","No support for routes defined outside standard Next.js directories","Middleware discovery limited to next.config.js and middleware.ts/js files","Subprocess management adds complexity — requires proper cleanup on client disconnect","Dev server output (stdout/stderr) may be voluminous; requires filtering/buffering","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.26,"ecosystem":0.3,"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.904Z","last_scraped_at":"2026-05-03T14:23:35.610Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-next-devtools-mcp","compare_url":"https://unfragile.ai/compare?artifact=npm-next-devtools-mcp"}},"signature":"U0erMcKacpJGVunZKDE+T/tEYfpFFX7dpwdicwUtfp9VBqdZ8ticm1k92+AX6Zh3q6uPSrzfO684a4joe3XiBA==","signedAt":"2026-06-23T08:48:50.432Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-next-devtools-mcp","artifact":"https://unfragile.ai/npm-next-devtools-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-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"}}