Next.js Architecture MCP
NPM · NEXTJS-MCP-ARCHITECTURE · SCANNED SEP 26
Indexes your Next.js project so an agent finds the file that owns a task in one call.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 4 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 775 tokens (~86/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Next.js Architecture MCP server?
Next.js Architecture MCP runs locally as an npm package, launched with npx -y nextjs-mcp-architecture. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · nextjs-mcp-architecture
claude mcp add hasimkilic-nextjs-mcp-architecture -- npx -y nextjs-mcp-architecture
{
"mcpServers": {
"hasimkilic-nextjs-mcp-architecture": {
"command": "npx",
"args": [
"-y",
"nextjs-mcp-architecture"
]
}
}
} {
"servers": {
"hasimkilic-nextjs-mcp-architecture": {
"command": "npx",
"args": [
"-y",
"nextjs-mcp-architecture"
]
}
}
} codex mcp add hasimkilic-nextjs-mcp-architecture -- npx -y nextjs-mcp-architecture
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hasimkilic-nextjs-mcp-architecture": {
"type": "local",
"command": [
"npx",
"-y",
"nextjs-mcp-architecture"
],
"enabled": true
}
}
} openclaw mcp add hasimkilic-nextjs-mcp-architecture --command npx --arg -y --arg nextjs-mcp-architecture
mcp_servers:
hasimkilic-nextjs-mcp-architecture:
command: "npx"
args: ["-y", "nextjs-mcp-architecture"] {
"McpServers": {
"hasimkilic-nextjs-mcp-architecture": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"nextjs-mcp-architecture"
]
}
}
} assistant mcp add hasimkilic-nextjs-mcp-architecture -t stdio -c npx -a -y nextjs-mcp-architecture
{
"mcpServers": {
"hasimkilic-nextjs-mcp-architecture": {
"command": "npx",
"args": [
"-y",
"nextjs-mcp-architecture"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 21 Sept 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 26 Sept 2026 · Analysed npm/nextjs-mcp-architecture@1.0.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_conventions Check files against this project ~79
Checks specific files for Next.js correctness problems (client/server boundary, server-only APIs, environment variables) and for deviations from this project's own conventions. Call after editing files and before reporting the work done.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | – |
| paths | array | yes | Project-relative paths of the files you changed. |
| projectRoot | string | – | – |
No output schema declared.
No examples provided.
find_symbol Find a symbol ~93
Locates where a component, hook, function or type is defined and which files use it, without reading whole files. Use instead of grepping for a name.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | – |
| limit | integer | – | Maximum files to return (1-5, default 3). |
| projectRoot | string | – | – |
| symbol | string | yes | Exact identifier, e.g. UserForm or useOrders. |
No output schema declared.
No examples provided.
get_project_context Get project context ~77
Reports which Next.js project this server resolved, how it was resolved, and which applications it contains. Call this first when a project-related answer looks wrong or empty.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Application name or workspace-relative path, for monorepos. |
| projectRoot | string | – | Absolute path, when the resolved project is wrong. |
No output schema declared.
No examples provided.
get_project_conventions Get project conventions ~104
Reports the conventions this project actually follows — file naming, where each kind of file lives, and the client/server boundary — each with the evidence behind it. Call before creating files so new code matches existing code.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | – |
| kind | string | – | Limit to one kind of convention. |
| projectRoot | string | – | – |
| section | string | – | Section id from a previous call, to read that part of the project docs in full. |
No output schema declared.
No examples provided.
get_project_profile Get project profile ~112
Reports this Next.js project's actual stack: version, router, path aliases, styling, UI kit, data and form libraries, ORM, i18n and test runners. Call before writing code so new files match what the project already uses.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Application name or path, for monorepos. |
| fields | array | – | Limit the answer to these sections. Omit for the one-line summary only. |
| projectRoot | string | – | Absolute path, when the resolved project is wrong. |
No output schema declared.
No examples provided.
get_route_context Get route context ~87
For a URL path, returns the page file that serves it, the layout/loading/error files that wrap it, and which parts are client components. Use before changing anything about a page.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | – |
| projectRoot | string | – | – |
| route | string | yes | URL path, e.g. /orders or /orders/[id] or /orders/42. |
No output schema declared.
No examples provided.
list_projects List candidate projects ~36
Lists every Next.js project root visible from this machine, with the evidence for each. Use when project resolution failed or picked the wrong project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_task_context Resolve task context ~131
Given a task in plain language, returns the few files that own it plus the conventions and verification commands that apply. Use this as the FIRST step for any implementation, bug-fix or refactor task instead of searching the codebase by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | Application name or path, for monorepos. |
| limit | integer | – | Maximum files to return (1-5, default 3). |
| projectRoot | string | – | Absolute path, when the resolved project is wrong. |
| task | string | yes | The task, in plain language. A sentence is better than a keyword. |
No output schema declared.
No examples provided.
set_project_root Pin the project root ~56
Pins the Next.js project root for the rest of this session, overriding automatic resolution. Use after list_projects when automatic resolution picked the wrong project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectRoot | string | yes | Absolute path to the project or monorepo root. |
No output schema declared.
No examples provided.
What is the Next.js Architecture MCP server?
Next.js Architecture MCP is listed in the public MCP registry as io.github.hasimkilic/nextjs-mcp-architecture. Indexes your Next.js project so an agent finds the file that owns a task in one call. This page covers its npm package (nextjs-mcp-architecture).
Is the Next.js Architecture MCP server safe to use?
Next.js Architecture MCP scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Next.js Architecture MCP server expose?
Next.js Architecture MCP exposes 9 tools: get_project_context, list_projects, set_project_root, get_project_profile, resolve_task_context, and 4 more. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.
Is the Next.js Architecture MCP server still maintained?
Next.js Architecture MCP is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.