Next.js Architecture MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 71 installs a week from npm.
Indexes your Next.js project so an agent finds the file that owns a task in one call.
Today is the operative word: we check Next.js Architecture MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add nextjs-mcp-architecture -- npx -y nextjs-mcp-architecture
{
"mcpServers": {
"nextjs-mcp-architecture": {
"command": "npx",
"args": [
"-y",
"nextjs-mcp-architecture"
]
}
}
}
[mcp_servers.nextjs-mcp-architecture]
command = "npx"
args = ["-y", "nextjs-mcp-architecture"]
{
"mcpServers": {
"nextjs-mcp-architecture": {
"command": "npx",
"args": [
"-y",
"nextjs-mcp-architecture"
]
}
}
}
{
"servers": {
"nextjs-mcp-architecture": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nextjs-mcp-architecture"
]
}
}
}
Lets your agent find the right MCP server, tool or service for a task, in one call. Ads labelled.
Finds the files a coding task touches, so your AI agent reads less. Local CLI and MCP server.
Find an AI agency for your next project.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
Indexes your project's markdown docs and serves them to any agent via local hybrid search.
The runtime your agent deploys to — DB, storage, and a public URL in one MCP call.
Local-first architecture guardrails and project context for JS/TS AI coding agents.
Architecture diagrams for your agent: draw on the live OpenFlowKit canvas or edit diagram files.
Answers built from our own checks of this server.