V
vertile-ai/next-mcp-server
Help LLMs to understand your Next apps better
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- 来源明细
- 收录自 abordage/awesome-mcp 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
我们收录于 2026-11-05;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# 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
## 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
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/vertile-ai-next-mcp-server/)
- 来源
- awesome · https://github.com/vertile-ai/next-mcp-server
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。