GitHub Next.js Optimizer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub Personal Access Token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analizar_repositorioB | Analiza un repositorio de GitHub completo y proporciona recomendaciones de optimización para proyectos Next.js y React |
| listar_archivos_reactB | Lista todos los archivos React/Next.js (.tsx, .jsx, .ts, .js) en un repositorio |
| analizar_archivoC | Analiza un archivo específico de React/Next.js y proporciona recomendaciones |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.