Skip to main content
Glama

nextscan

MCP-Server, der Next.js-Projekte scannt und eine kompakte Zusammenfassung zurückgibt. Ein Tool-Aufruf → vollständige Projektübersicht.

Was es tut

Ohne nextscan

Mit nextscan

Manuelle Datei-für-Datei-Erkundung

Einzelner scan-Aufruf

Mehrere Tool-Aufrufe, um Routen zu verstehen

Kompakter Routenbaum mit Flags

Übersehene Sicherheitsprobleme

Hartcodierte Geheimnisse + Erkennung von Env-Leaks

Unbekannte API-Abdeckung

Auth + Validierungsstatus pro Endpunkt

Schema-Ratespiel

Prisma/Drizzle-Beziehungszuordnung

Related MCP server: guardvibe

Schnellinstallation

# Clone and build
cd nextscan
npm install
npm run build

# Add to Claude Code
claude mcp add nextscan -- node /path/to/nextscan/dist/index.js

Tool: scan

Parameter

Typ

Erforderlich

Beschreibung

path

string

Ja

Absoluter Pfad zum Next.js-Projektstamm

focus

enum

Nein

routes | api | schema | security

Beispielausgabe

nextscan — my-app
────────────────────────────────────────
Root: /Users/dev/my-app
   src/ : yes  app/ : yes  middleware: yes
   ORM  : prisma

Routes
   Pages: 12  Layouts: 3  API: 5
   Dynamic: 4  Static: 8
   Client: 3  Server: 9
   Groups: (marketing), (auth)
   Matchers: /dashboard/:path*, /api/:path*
   ┌─ Pages
   ├─ /
   ├─ /about
   ├─ /dashboard [client]
   ├─ /blog/[slug] [dyn,SSG]
   └─ /settings [client]

API Endpoints
   Total: 5  Unprotected: 1
   ├─ GET,POST /api/users [auth:next-auth | val:zod]
   ├─ GET /api/health [no-auth,no-rate-limit]
   └─ POST /api/webhook [no-auth,no-validation]

Schema
   Models: 5  Relations: 4
   Orphans: AuditLog
   User ─< Post (1:N)
   User ─ Profile (1:1)
   Post >─< Tag (N:N)

Security
   Score: 75/100  Headers: yes  Middleware: yes
   [high] API route /api/health has no auth: [GET]
   [medium] No rate limiting on /api/users

Beispiel-Prompts

  • "Scanne mein Next.js-Projekt unter /Users/dev/my-app"

  • "Überprüfe die Sicherheit meiner Next.js-App"

  • "Zeig mir die Routenstruktur"

  • "Analysiere das Datenbankschema"

Architektur

src/
├── index.ts              # MCP server entry point
├── tools/scan.ts         # Orchestrator
├── analyzers/
│   ├── routes.ts         # App router analysis
│   ├── api.ts            # API endpoint analysis
│   ├── schema.ts         # Schema orchestration
│   └── security.ts       # Security scanning
├── parsers/
│   ├── typescript.ts     # ts-morph utilities
│   ├── prisma.ts         # Regex-based Prisma parser
│   └── drizzle.ts        # AST-based Drizzle parser
├── formatters/
│   └── compact.ts        # Unicode tree formatter
└── utils/
    ├── fs.ts             # File system utilities
    └── detect.ts         # Project detection

Anforderungen

  • Node.js 18+

  • Ein MCP-kompatibler Client (Claude Code, Claude Desktop usw.)

Entwicklung

npm install
npm run build
npm test
npm run test:coverage

Autor

Berkay Derin — github.com/berkayderin

Lizenz

MIT

Available Tools

1 tool
scanA

Scan a Next.js project and return a compact summary of routes, API endpoints, schema, and security issues

Inputs: path (required), focus.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The single tool has a clear, distinct purpose of scanning a Next.js project.

    Naming Consistency5/5

    Only one tool exists, so naming is inherently consistent. The verb 'scan' clearly indicates the action.

    Tool Count1/5

    A single tool is extremely thin for a server, suggesting the surface is severely underdeveloped. Even if the purpose is narrow, most useful servers would expose multiple operations.

    Completeness3/5

    The scan tool provides a comprehensive overview of a Next.js project, but it is a read-only operation. Missing other aspects like specific security fix suggestions or detailed endpoint management, leaving notable gaps for deeper workflows.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A utility tool that analyzes Next.js application routes and provides detailed information about API paths, HTTP methods, parameters, status codes, and request/response schemas.
      99
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Security MCP server with 300+ rules for AI-generated code. Scans Next.js, Supabase, Clerk, Stripe, Prisma, Hono, GraphQL and 20+ modules. Zero config, runs locally.
      39
      1,244 npm
      6
      Apache 2.0
    • 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.
      MIT