@ld338/nextjs MCP Server

@ld338

Repository

Basic information

About @ld338/nextjs MCP Server

No overview available yet

#nextjs #mcp-server #development-tools

@ld338/nextjs MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "nextjs-mcp-server": {
      "command": "npx",
      "args": [
        "next",
        "--version"
      ]
    }
  }
}

@ld338/nextjs MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is @ld338/nextjs-mcp-server?

A Model Context Protocol (MCP) server for managing Next.js development servers with comprehensive error monitoring. It allows you to start, stop, restart, and monitor multiple Next.js dev servers programmatically or via MCP-compatible clients like Claude, Copilot, or custom tools.

How to use @ld338/nextjs-mcp-server?

Install globally via npm, yarn, or pnpm, then configure your MCP client (e.g., Claude Desktop or GitHub Copilot) to use the nextjs-mcp-server command. Once configured, issue natural-language commands (like “start a Next.js server in the current directory”) or send MCP tool requests directly. The server communicates over stdio.

Key features of @ld338/nextjs-mcp-server

Start, stop, restart Next.js dev servers in any directory
List all running servers with status, uptime, and performance
Automatic port detection and conflict resolution
Real-time logs and error tracking for managed servers
Full support for Next.js Turbo mode
Cross-platform on Windows, macOS, and Linux

Use cases of @ld338/nextjs-mcp-server

Manage multiple Next.js dev servers simultaneously from an AI assistant
Automate server lifecycle during CI/CD or local development workflows
Remotely inspect server logs and errors using MCP‑compatible tools
Integrate Next.js server control into custom developer tooling or editors

Frequently asked questions

What are the system requirements?

Node.js 18.0.0 or higher, Next.js 12.0.0 or higher in managed projects, and Windows 10+, macOS 10.15+, or Linux (Ubuntu 18.04+).

How do I configure it for Claude Desktop?

Add a `"nextjs-manager"` entry under `"mcpServers"` in your Claude Desktop config file (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS) with `"command": "nextjs-mcp-server"`.

What if a server won’t start?

Check if the port is already in use (e.g., `netstat -an | grep :3000`) and verify the Next.js installation (`npx next --version`). The server provides detailed error messages for invalid projects or port conflicts.

Where are running servers tracked?

In `~/.nextjs-mcp-servers.json`. This file is updated on start and stop, and stale processes are automatically removed. Only servers started via this tool are logged.

Can I use the server with GitHub Copilot?

Yes. Add a `"nextjs-manager"` entry under `"mcp.servers"` in your Copilot configuration with `"command": "nextjs-mcp-server"`.

Comments

More Other MCP servers

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.