Skip to main content
Glama
vercel

Next.js DevTools MCP

Official
by vercel

Related Servers

Alternatives to Next.js DevTools MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides current Next.js 16 documentation to AI assistants, enabling version-accurate lookups, code generation, and configuration guidance for App Router, Pages Router, Server Components, and Tailwind CSS v4.
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to automate Next.js development including project scaffolding, React component generation, API route creation, and full-stack application workflows with TypeScript and Tailwind CSS support.
      MIT
    • A
      license
      Not graded
      quality
      B
      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.
      4 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI agents with access to a comprehensive database of 200+ Next.js documentation URLs for intelligent document selection and retrieval. Enables Claude and other AI assistants to analyze user queries and recommend the most relevant Next.js documentation pages.
      1
      11 npm
      13
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Monitors Next.js development servers with intelligent error categorization, smart diagnostics, and performance tracking.
      8
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      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 comprehensive documentation with AI-powered guidance.
      -

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: browser automation via CLI, executing MCP tools on the dev server, accessing local documentation, and discovering running servers and tools. There is no overlap or ambiguity.

    Naming Consistency4/5

    Tools use a consistent snake_case convention. Three tools share the 'nextjs_' prefix, while 'browser_eval' deviates slightly but still follows the same pattern. The naming is predictable and readable.

    Tool Count5/5

    With 4 tools, the set is well-scoped for a Next.js DevTools MCP server. Each tool covers a necessary aspect: discovery, execution, documentation access, and browser automation. No redundant or missing tools.

    Completeness5/5

    The tool surface covers the primary needs for interacting with a Next.js development environment: discovering server state, executing diagnostics, accessing version-accurate docs, and automating browser testing. There are no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive