Next.js Architecture MCP

io.github.hasimkilicPublished by GitHub account hasimkilicv1.0.7Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that indexes a Next.js project so an assistant can locate the file responsible for a given task in a single call.

What you can do
Indexes the Next.js project on the local machine so the assistant can find relevant files quickly. Lets the assistant locate the file that owns a specific task in one call instead of searching the codebase step by step. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when working in a Next.js codebase and you want the assistant to jump straight to the right file for a change or question, rather than scanning the project manually.
Requirements
Runs as a local process over stdio, installed from the npm package nextjs-mcp-architecture, so Node.js and npm are needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
It indexes your project locally, so the assistant gains visibility into your source files; review what the index covers before use. No credentials or write actions are declared, but the tool list is not published, so confirm its behavior before installing.

Installation

In SourceWeft

  1. Open Next.js Architecture MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.7LatestSep 21, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.