About Next.js MCP Server
Next.js MCP Server is an MCP server that analyzes Next.js App Router projects so LLMs can better understand the app's API routes. It scans the app directory and extracts paths, HTTP methods, parameters and comment-based documentation. It suits developers who want AI tools to see their Next.js API structure.
Key features
- 01get-routers-info tool scans API routes
- 02Extracts paths and HTTP methods
- 03Reports request parameters and status codes
- 04Reads request and response schemas
- 05Extracts documentation from code comments
Use cases
- 01Let an AI assistant list the API routes in a project
- 02Give Cursor context about a Next.js API structure
MCP support
As an MCP server, it returns structured API route information to MCP clients through the get-routers-info tool.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMENext.js MCP Server
Demo

Features
-
get-routers-infoThe 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
npm install next-mcp-server
Or if you're using pnpm:
pnpm add next-mcp-server
Usage
Command Line
You can run the mcp server directly:
npm run build
node dist/index.js
Docker
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:
[
{
"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:
npm run test
To run the mcp server locally:
npm run build
node dist/index.js
To run it from node_modules after npm i:
node node_modules/next-mcp-server/dist/index.js
To run the playground:
pnpm --filter playground dev
How It Works
The tool:
- Scans your Next.js app directory structure for route files
- Analyzes each route file to extract HTTP methods, paths, parameters, etc.
- Extracts documentation from comments
- Returns a structured representation of all your API routes
Restrictions
- Due to the nature of accessing filesystem directory by path, it will not work if hosted over network
- Only supports Next.js App router projects
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.