GitHub Next.js Optimizer MCP Server
Related Servers
Alternatives to GitHub Next.js Optimizer MCP Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceAutomatically 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 documentation with performance guidance.-
- 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.-
- AlicenseCqualityBmaintenanceEnables auditing Next.js codebases for SEO and AI-readiness (AEO), scoring crawlability, extractability, and citation readiness, and generating advise-only fix diffs the coding agent applies. Supports planning content briefs, schema, and internal links, then re-auditing to verify which findings were fixed, remained, or regressed without ever writing to the repo.23MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repository structures and read file contents with features like directory traversal, file type analysis, syntax highlighting, and code pattern detection. Supports both public and private repositories through GitHub API integration.8 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides code analysis for Next.js projects through the Model Context Protocol, enabling IDE and LLM integration to identify unused files, dead code, and redundant API endpoints.24 npm8MIT
- AlicenseAqualityDmaintenanceEnables analysis of any GitHub repository to get architecture, file roles, execution flows, system design Q\&A, and structured agent context. Works with MCP-compatible clients like Claude Desktop, Cursor, and Windsurf.647 npm1MIT
TDQS
Scored across 3 tools
The three tools have distinct scopes: whole-repository analysis, file listing, and single-file analysis. However, 'analizar_repositorio' and 'analizar_archivo' both provide optimization recommendations and could be confused if an agent isn't careful about the target scope.
All tool names follow a consistent Spanish verb_noun pattern in snake_case: analizar_repositorio, listar_archivos_react, analizar_archivo. No deviations or mixed conventions.
Three tools is a reasonable, focused set for a specialized Next.js/React optimizer. It is on the thin side but each tool has a clear role, and the count aligns well with the narrow domain.
The surface covers analysis of repos and files plus file listing, which addresses the core need of providing recommendations. However, notable gaps exist: no tools for applying fixes, analyzing dependencies (e.g., package.json), inspecting Next.js configuration, or generating structured reports, which limits the 'optimizer' workflow.