Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
V

vertile-ai/next-mcp-server

Help LLMs to understand your Next apps better

Before you install: no copy-paste command · no license recorded · link reachable

First step: npm install next-mcp-server

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site

We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →

Source
collected from the abordage/awesome-mcp list · type: MCP server
Harvest history
first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
Score
score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# Next.js MCP Server

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

## Demo
## Features
get-routers-info
The Router Analyzer scans your Next.js app directory structure and extracts information about all API routes, including:
API paths
HTTP methods (GET, POST, PUT, DELETE, etc.)
Request parameters
Status codes
Request and response schemas
## Installation
bash
npm install next-mcp-server
Or if you're using pnpm:
bash
pnpm add next-mcp-server
## Usage
### Command Line
You can run the mcp server directly:
bash
npm run build
node dist/index.js
### Docker
bash
docker build -t mcp/next -f Dockerfile .
docker run mcp/next -d
For cursor usage, define a mcp.json under ~/.cursor or [projectDir]/.cursor
"mcpServers": {
"next.js": {
"url": "http://localhost:4857/sse"
The url here could vary based on your .env settings within the project.
## Output
The tool generates detailed information about each route:
javascript
"filePath": "/path/to/your/app/api/test/route.ts",
"implementationPath": "/path/to/your/app/api/test/route.ts",
"apiPath": "/api/test",
"handlers": [
"method": "GET",
"path": "/api/test",
"functionSignature": "export async function GET(request: Request)",
"description": "Get test data",
"parameters": [],
"statusCodes": [200]
},
"method": "POST",
"path": "/api/test",
"functionSignature": "export async function POST(request: Request)",
"description": "Create test data",
"parameters": [],
"requestBodySchema": "{ name: string }",
"statusCodes": [201, 400]
## Development
To run tests:
bash
npm run test
To run the mcp server locally:
bash
npm run build
node dist/index.js
To run it from nodemodules after npm i:
bash
node nodemodules/next-mcp-server/dist/index.js
To run the playground:
bash
pnpm --filter playground dev
## How It Works
The tool:
1. Scans your Next.js app directory structure for route files
2. Analyzes each route file to extract HTTP methods, paths, parameters, etc.
3. Extracts documentation from comments
4. Returns a structured representation of all your API routes
## Restrictions
1. Due to the nature of accessing filesystem directory by path, it will not work if hosted over network
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/vertile-ai-next-mcp-server/)
Source
awesome · https://github.com/vertile-ai/next-mcp-server
Browse by field
MCP servers
Listed by
10 independent sources
added
today

More like this

All 6,229 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index