# Next.js Architecture MCP (npm · nextjs-mcp-architecture)

Indexes your Next.js project so an agent finds the file that owns a task in one call.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `nextjs-mcp-architecture`: 61/100 (this document), [markdown](https://verifymcp.io/servers/hasimkilic-nextjs-mcp-architecture/nextjs-mcp-architecture.md), [page](https://verifymcp.io/servers/hasimkilic-nextjs-mcp-architecture/nextjs-mcp-architecture)

## Channel facts

- Registry: `npm`
- Package: `nextjs-mcp-architecture`
- Version: `1.0.7`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license.
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 775 tokens (~86/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add hasimkilic-nextjs-mcp-architecture -- npx -y nextjs-mcp-architecture
```

### Cursor

```json
{
  "mcpServers": {
    "hasimkilic-nextjs-mcp-architecture": {
      "command": "npx",
      "args": [
        "-y",
        "nextjs-mcp-architecture"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hasimkilic-nextjs-mcp-architecture": {
      "command": "npx",
      "args": [
        "-y",
        "nextjs-mcp-architecture"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hasimkilic-nextjs-mcp-architecture -- npx -y nextjs-mcp-architecture
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hasimkilic-nextjs-mcp-architecture": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "nextjs-mcp-architecture"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hasimkilic-nextjs-mcp-architecture --command npx --arg -y --arg nextjs-mcp-architecture
```

### Hermes

```yaml
mcp_servers:
  hasimkilic-nextjs-mcp-architecture:
    command: "npx"
    args: ["-y", "nextjs-mcp-architecture"]
```

### Netclaw

```json
{
  "McpServers": {
    "hasimkilic-nextjs-mcp-architecture": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "nextjs-mcp-architecture"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hasimkilic-nextjs-mcp-architecture -t stdio -c npx -a -y nextjs-mcp-architecture
```

### Other

```json
{
  "mcpServers": {
    "hasimkilic-nextjs-mcp-architecture": {
      "command": "npx",
      "args": [
        "-y",
        "nextjs-mcp-architecture"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 61, +11)

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 1.00

### 2026-09-21 (score 50)

First indexed and scored.

## MCP tools (9)

### `get_project_context` (~77 tokens)

Get project context

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.

Input parameters:

- `app` (string): Application name or workspace-relative path, for monorepos.
- `projectRoot` (string): Absolute path, when the resolved project is wrong.

### `list_projects` (~36 tokens)

List candidate projects

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.

### `set_project_root` (~56 tokens)

Pin the project root

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.

Input parameters:

- `projectRoot` (string, required): Absolute path to the project or monorepo root.

### `get_project_profile` (~112 tokens)

Get project profile

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.

Input parameters:

- `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.

### `resolve_task_context` (~131 tokens)

Resolve task context

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.

Input parameters:

- `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, required): The task, in plain language. A sentence is better than a keyword.

### `find_symbol` (~93 tokens)

Find a symbol

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.

Input parameters:

- `app` (string)
- `limit` (integer): Maximum files to return (1-5, default 3).
- `projectRoot` (string)
- `symbol` (string, required): Exact identifier, e.g. UserForm or useOrders.

### `get_route_context` (~87 tokens)

Get route context

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.

Input parameters:

- `app` (string)
- `projectRoot` (string)
- `route` (string, required): URL path, e.g. /orders or /orders/[id] or /orders/42.

### `get_project_conventions` (~104 tokens)

Get project conventions

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.

Input parameters:

- `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.

### `check_conventions` (~79 tokens)

Check files against this project

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.

Input parameters:

- `app` (string)
- `paths` (array, required): Project-relative paths of the files you changed.
- `projectRoot` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/hasimkilic-nextjs-mcp-architecture/nextjs-mcp-architecture#diagnostics

## Score history

- 2026-09-26: 61
- 2026-09-25: 61
- 2026-09-24: 61
- 2026-09-23: 61
- 2026-09-22: 61
- 2026-09-21: 50

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/nextjs-mcp-architecture
- Socket report: https://socket.dev/npm/package/nextjs-mcp-architecture
- Website: https://nextjs-mcp.com/
- Changelog RSS feed: https://verifymcp.io/servers/hasimkilic-nextjs-mcp-architecture/nextjs-mcp-architecture.xml
- Changelog JSON feed: https://verifymcp.io/servers/hasimkilic-nextjs-mcp-architecture/nextjs-mcp-architecture.json
- HTML version of this page: https://verifymcp.io/servers/hasimkilic-nextjs-mcp-architecture/nextjs-mcp-architecture