Skip to main content
Glama
souvikdu

perfonext-build-mcp

by souvikdu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to perfonext-build-mcp

Related Servers

  • nextscan

    berkayderin
    A
    license
    A
    quality
    D
    maintenance
    MCP server that scans Next.js projects and returns a compact summary of routes, API endpoints, schema, and security issues.
    1
    33 npm
    1
    MIT

  • Next.js MCP Server

    kamolc4
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-compatible clients to inspect Next.js codebases, analyze App Router and Pages Router structure, discover API routes, and audit build performance through controlled tools.
    12 npm
    MIT

  • unplugin-mcp

    situ2001
    A
    license
    Not graded
    quality
    D
    maintenance
    Creates and manages an MCP server integrated with build tools (Rollup, Vite, Webpack, etc.) to enable AI assistants to analyze, inspect, and control the build process.
    2,813 npm
    31
    MIT

  • @registry/mcp

    broisnischal
    A
    license
    Not graded
    quality
    D
    maintenance
    Unified MCP server for searching, analyzing, and managing packages across npm, JSR, Deno, and multiple CDN providers with auto-detection.
    MIT

  • codebase-lens

    shanewin
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables deep, AST-based analysis of Next.js projects so MCP clients can understand route hierarchies, client/server boundaries, auth coverage, unused exports, and security issues directly from the codebase.
    150 npm
    MIT
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have clearly distinct purposes, but compare_builds and explain_growth overlap in analyzing build differences, and get_shared_chunks vs explain_shared_chunks could be confused at first glance. The descriptions and dependency notes help disambiguate, so it is mostly clear.

Naming Consistency4/5

Tool names largely follow a verb_noun snake_case pattern, with load_, get_, compare_, explain_, and suggest_ prefixes. The one outlier is how_to_collect_stats, which uses a non-standard how_to_ prefix but remains readable and understandable.

Tool Count5/5

With 11 tools, the server is well-scoped for its purpose of Next.js bundle analysis. Each tool contributes to a distinct part of the workflow: data collection, loading stats, analysis, comparison, and optimization recommendations.

Completeness5/5

The tool set covers the full analysis lifecycle: collecting stats, loading build and webpack data, identifying large routes and shared chunks, finding duplicates, tracing imports, comparing builds, explaining growth, and suggesting optimizations. No significant gaps are apparent for the stated domain.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources