
Nextscan
- 1 repo stars
- Updated March 1, 2026
- berkayderin/nextscan
Nextscan is an MCP server that scans local Next.js projects and returns a compact summary your coding agent can cite before making changes.
About
Nextscan is an MCP server that inspects a Next.js project on disk and returns a compact summary your AI coding agent can use as shared context. developers shipping App Router or Pages Router apps often waste turns listing folders, reading config, and guessing how the repo is organized before every change. Registering this server in Claude Code, Cursor, Codex, or another MCP client lets the model request that summary in one step instead of piecing the picture together file by file. It targets developers who already run Next.js locally and want faster onboarding for agents during builds, pre-ship reviews, and small-team handoffs. The package uses stdio transport and is published on npm, so setup is a standard Node install plus MCP config—no hosted service implied by the registry metadata. Pair it with your existing edit and test workflow when you need reliable structure awareness before refactors, dependency upgrades, or documentation tasks.
- stdio MCP server installable from npm as @berkayderin/nextscan (v1.0.1)
- Scans a local Next.js project and returns a compact summary for agent context
- Reduces token-heavy manual repo exploration in Claude Code, Cursor, and Codex
- Works against real project directories on your machine—no separate SaaS dashboard
- Lightweight integration: add one MCP entry pointing at the published npm package
Nextscan by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add nextscan -- npx -y @berkayderin/nextscanAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | @berkayderin/nextscan |
| Transport | STDIO |
| Auth | None |
| Last updated | March 1, 2026 |
| Repository | berkayderin/nextscan ↗ |
What it does
Give Claude Code or Cursor a one-call snapshot of a local Next.js repo so the agent can plan refactors, reviews, or new features without manually opening dozens of files.
Who is it for?
Best when you use Claude Code or Cursor on a Next.js codebase and want quick, repeatable project summaries during implementation and cleanup.
Skip if: Skip if you do not use Next.js, need deep runtime profiling, or want a hosted security audit rather than local project introspection.
What you get
After you add the MCP server, your agent can pull a single compact Next.js project summary and work from accurate structure instead of exploratory file reads.
- Compact textual summary of the scanned Next.js project for agent sessions
- Faster agent onboarding to routes, config, and overall repo shape
- Repeatable MCP-backed project scan without custom scripts
By the numbers
- Published MCP server version 1.0.1 on the MCP registry schema 2025-12-11
- Single npm package @berkayderin/nextscan with stdio transport
- Source repository: github.com/berkayderin/nextscan
README.md
nextscan
MCP server that scans Next.js projects and returns a compact summary. One tool call → full project overview.
What it does
| Without nextscan | With nextscan |
|---|---|
| Manual file-by-file exploration | Single scan call |
| Multiple tool calls to understand routes | Compact route tree with flags |
| Missing security issues | Hardcoded secrets + env leak detection |
| Unknown API coverage | Auth + validation status per endpoint |
| Schema guesswork | Prisma/Drizzle relation mapping |
Quick Install
# 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 | Type | Required | Description |
|---|---|---|---|
path |
string | Yes | Absolute path to Next.js project root |
focus |
enum | No | routes | api | schema | security |
Example Output
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
Example Prompts
- "Scan my Next.js project at /Users/dev/my-app"
- "Check the security of my Next.js app"
- "Show me the route structure"
- "Analyze the database schema"
Architecture
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
Requirements
- Node.js 18+
- An MCP-compatible client (Claude Code, Claude Desktop, etc.)
Development
npm install
npm run build
npm test
npm run test:coverage
Author
Berkay Derin — github.com/berkayderin
License
MIT
Recommended MCP Servers
How it compares
MCP integration for Next.js repo introspection, not an in-editor skill or a generic web-scraping automation server.
FAQ
Who is nextscan for?
Nextscan is for developers who build with Next.js and use MCP-enabled agents such as Claude Code, Cursor, or Codex and want structured project context without manual exploration.
When should I use nextscan?
Use nextscan when you start a new agent session on a Next.js repo, before large refactors, dependency upgrades, or when you need a quick orientation summary during the build or ship phases.
How do I add nextscan to my agent?
Install @berkayderin/nextscan from npm, configure your MCP client with stdio pointing at that package per your editor’s MCP settings, then invoke the server’s scan capability against your local Next.js project path.