Skip to main content
Glama

Related Servers

Alternatives to midnight-nextjs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides specialized development tools and utilities for Next.js, allowing AI agents to perform runtime diagnostics and access official documentation. It enables automated context initialization and real-time interaction with Next.js development servers to query application state.
      4
      77,455 npm
      818
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time debugging, code quality monitoring, and performance insights for React/Next.js applications with features including Chrome DevTools integration, breakpoint management, complexity analysis, and live error streaming.
      5 npm
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform Web3 development operations such as toolchain diagnostics, chain registry queries and live probing, address validation, secret scanning, deployment logging, and standards searches across multiple blockchains.
      15 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.
      8 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Monitors Next.js development servers with intelligent error categorization, smart diagnostics, and performance tracking.
      8
      MIT

    TDQS

    B3.3/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is direct overlap between midnight-search-docs and midnight_search_docs, which ambiguously serve the same function. Additionally, the mix of Next.js and Midnight tools with similar prefixes (init vs midnight_init) could cause confusion.

    Naming Consistency3/5

    Naming conventions are inconsistent: some Midnight tools use underscores (midnight_analyze_contract) while others use hyphens (midnight-docs-status). Next.js tools use underscores, and general tools also use underscores. This mix of patterns reduces predictability.

    Tool Count2/5

    With 35 tools covering two distinct domains (Next.js and Midnight), the count exceeds the recommended upper bound of 25. While each domain individually has a reasonable number, the combined surface is too large for a single server.

    Completeness3/5

    The Next.js tools cover common workflows (indexing, calling, docs, upgrade) and the Midnight tools cover contract lifecycle and network queries. However, there are notable gaps like missing contract deletion or event log retrieval, and the duplicate search tool suggests incomplete rationalization.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues