"Next.js" matching MCP servers:

Automatically 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.

Analyze React render performance in Next.js apps. Detects rerender storms, commit spikes, and slow components.

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.

An MCP server that lets an AI agent drive and inspect a running Next.js app, with headless route/error introspection and a real DOM-based in-page bridge for interactive testing.

Enables static auditing of Razorpay payment integrations in Next.js App Router projects written in TypeScript.

Enables coding agents to locate the right files and conventions in a Next.js project in a single call, drastically reducing token usage compared to searching.

Enables database interaction for a Next.js application using Prisma, supporting queries and mutations through natural language.

Gives AI coding assistants live access to the Hyperiux Vault catalog of React and Next.js animation effects. Search effects, inspect dependencies and installation instructions, and retrieve source for free effects.

Analyze V8/Chrome CPU profiles in Next.js & Node.js apps. Hotspots, package cost attribution, and optimization suggestions for MCP clients like Claude Code and GitHub Copilot

Static security scanner for AI-generated (vibe-coded) Supabase and Next.js apps. Runs as an MCP server so an LLM can scan, explain findings, and produce fixes while it writes code, all locally and offline.

Probes your live API and classifies why each endpoint failed (root cause, evidence, and a calibrated confidence level), exposed over MCP so your AI assistant debugs from evidence instead of guessing. Works with FastAPI, Express, Next.js, tRPC, and GraphQL.

Enables AI coding agents to observe real-time Node, Vite, Next.js, Storybook, TypeScript, and browser runtime errors from a wrapped dev server, source-mapped to exact file, line, and column with the log lines preceding each crash. It exposes MCP tools for listing open errors, fetching full stack details, and checking or marking fixes as resolved, all locally with no code changes.

MCP server that scans Next.js projects and returns a compact summary of routes, API endpoints, schema, and security issues.

A comprehensive MCP server for frontend analysis. It provides Google Lighthouse audits, code quality checks, SEO metadata verification, accessibility analysis, and bundle optimization for React and Next.js projects.

MCP Server for Next.js build & bundle analysis. Chunk size, shared chunk attribution, and code-split suggestions for MCP clients

Framework-aware code intelligence MCP server that builds a cross-language dependency graph from source code. 53 integrations (Laravel, Django, Rails, Spring, NestJS, Next.js, and more) across 68 languages. 100+ tools for navigation, impact analysis, refactoring, security scanning, session memory, and CI/PR reports — up to 97% token reduction.

Enables coding agents to capture a live website's rendered frontend, export it as an editable Next.js or Astro project, and re-verify the result pixel by pixel to confirm visual fidelity held.

Persistent daemon that compresses codebases via AST body folding before indexing them for AI coding assistants like Claude Code and Cursor 57-89% token reduction with sub-millisecond queries, verified on Django, Spring, and Next.js.

Enables coding agents to run Playwright e2e tests, validate Supabase RLS policies with role-based SQL, typecheck TypeScript, execute npm scripts with parsed test output, and validate Next.js builds, all through a structured MCP interface.

Indexes any TypeScript / React / Next.js repo into a queryable code graph and exposes 13 MCP tools — who-renders, who-calls, find-references, blast-radius, find-cycles, dead-code orphans, and local semantic search — so agents query structure instead of reading whole files. Built on ts-morph, so edges are resolved, not grepped.