Next.js Documentation

Next.js Documentation

nanameru

Gives AI agents access to 200+ Next.js documentation URLs organized by category, allowing them to intelligently select and reference the most relevant docs for user questions.

Provides structured access to Next.js documentation URLs organized by categories including routing, data fetching, API routes, deployment, and optimization, enabling accurate responses grounded in current Next.js documentation.

12272 views4RemoteLocal (stdio)

What it does

  • Retrieve organized Next.js documentation URLs by category
  • Enable AI agents to select relevant docs based on user queries
  • Access documentation for routing, data fetching, API routes, and deployment
  • Provide comprehensive coverage of Next.js features and concepts

Best for

Next.js developers seeking accurate documentation referencesAI assistants answering Next.js technical questionsCode editors with AI features for Next.js development
200+ documentation URLs includedNo external API calls requiredRun via npx with zero setup

About Next.js Documentation

Next.js Documentation is a community-built MCP server published by nanameru that provides AI assistants with tools and capabilities via the Model Context Protocol. Access organized Next.js documentation on routing, API routes, deployment & more. Find the latest Next.js doc resources It is categorized under developer tools. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.

How to install

You can install Next.js Documentation in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport. This server supports remote connections over HTTP, so no local installation is required.

License

Next.js Documentation is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.

Tools (1)

get_all_docs

Provide all Next.js documentation URLs for AI agents. Auto-trigger guidance (for clients): - Run when the user asks about 'Next.js', 'Nextjs', 'Next', or mentions topics like 'App Router', 'Pages Router', 'Route Handlers', 'data fetching', 'deployment', 'turbopack', 'Vercel'. - Run when the user reports errors containing keywords like 'Next.js error', 'build error', 'routing error', 'hydration error', 'module not found', 'next.config.js', 'middleware', 'Image', 'Link', 'Route Handler'. - Run when an active file path suggests a Next.js app, e.g. 'next.config.js', 'app/**', 'pages/**', 'middleware.ts/js', or imports starting with 'next/'. Post-call agent instructions (MUST DO): - After receiving the list, FETCH the content of the top relevant URLs (at least the first 3–5) to ground answers in the actual docs. - Use standard HTTP GET with a 10s timeout, follow redirects, and limit concurrency to 3 to be polite. - Prefer pages whose title/URL matches the user's query or error message; summarize only after fetching. - If fetching fails, try the next candidate URL and report which ones were fetched. This tool returns a comprehensive list so the agent can pick and fetch the most relevant docs.

Next.js Docs MCP

A Model Context Protocol (MCP) server that provides all Next.js documentation URLs to AI agents like Claude for intelligent document selection. This server contains a comprehensive static database of Next.js documentation pages and enables AI agents to analyze and select the most relevant documentation based on user queries.

Key Features

  • AI Agent Integration: Provides all documentation URLs for Claude and other AI agents to analyze and select relevant docs
  • Comprehensive Static Database: Contains 200+ Next.js documentation URLs across all categories
  • No External Dependencies: Pure static URL database with no API calls or crawling required
  • Claude-Optimized: Specifically designed for Claude to intelligently select relevant documentation
  • npx-Ready: No local installation needed - run via npx from any MCP client

Requirements

  • Node.js 18 or newer
  • VS Code, Cursor, Windsurf, Claude Desktop, Goose, LM Studio, or any other MCP client

Getting Started

Installation

Standard config works in most tools:

{
  "mcpServers": {
    "nextjs-docs-mcp": {
      "command": "npx",
      "args": ["@taiyokimura/nextjs-docs-mcp@latest"]
    }
  }
}

Install in VS Code Install in VS Code Insiders

Client-Specific Setup

Claude Code (Recommended)

Use the Claude Code CLI to add the MCP server:

claude mcp add nextjs-docs-mcp -- npx @taiyokimura/nextjs-docs-mcp@latest

Remove if needed:

claude mcp remove nextjs-docs-mcp
Claude Desktop

Follow the MCP install guide and use the standard config above.

Cursor

Go to Cursor SettingsMCPAdd new MCP Server.

Use the following:

  • Name: nextjs-docs-mcp
  • Type: command
  • Command: npx
  • Args: @taiyokimura/nextjs-docs-mcp@latest
  • Auto start: on (optional)
VS Code

Add via CLI:

code --add-mcp '{"name":"nextjs-docs-mcp","command":"npx","args":["@taiyokimura/nextjs-docs-mcp@latest"]}'

Or use the install links above.

LM Studio

Add MCP Server with:

  • Command: npx
  • Args: ["@taiyokimura/nextjs-docs-mcp@latest"]
Goose

Advanced settings → Extensions → Add custom extension:

  • Type: STDIO
  • Command: npx
  • Args: @taiyokimura/nextjs-docs-mcp@latest
  • Enabled: true
opencode

Example ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nextjs-docs-mcp": {
      "type": "local",
      "command": [
        "npx",
        "@taiyokimura/nextjs-docs-mcp@latest"
      ],
      "enabled": true
    }
  }
}
Qodo Gen

Open Qodo Gen → Connect more tools → + Add new MCP → Paste the standard config above → Save.

Windsurf

Follow Windsurf MCP documentation and use the standard config above.

Available Tools

1. get_all_docs

Get all Next.js documentation URLs for AI agents to analyze and select relevant ones.

Parameters:

  • None required

Description: This tool returns a comprehensive list of all Next.js documentation URLs organized by categories. AI agents like Claude can use this list to analyze user queries and select the most relevant documentation pages. The tool provides structured data including titles, URLs, descriptions, and categories for intelligent document selection.

Response Format: The tool returns a formatted list containing:

  • Document titles
  • Direct URLs to Next.js documentation
  • Brief descriptions
  • Category classifications
  • Total count of available documents

Usage Examples

Get all Next.js documentation URLs:

{
  "tool": "get_all_docs"
}

Claude Integration Example:

  1. User asks: "Next.jsのエラーを解消したいです"
  2. Claude calls: get_all_docs
  3. MCP server returns: All 200+ Next.js documentation URLs with titles, descriptions, and categories
  4. Claude analyzes the list and selects relevant documents:
    • "Getting Started: Error Handling"
    • "Routing: Error Handling"
    • "API Routes Error Handling"
  5. Claude provides targeted documentation links to the user

Integration with Claude Code:

# Claude Code内で使用
claude mcp add nextjs-docs-mcp -- npx @taiyokimura/nextjs-docs-mcp@latest

Then Claude can automatically call the tool when users ask Next.js-related questions.

Development

Building the Package

npm run build

Publishing to npm

  1. Update the package name in package.json to your scope (e.g., @taiyokimura/nextjs-docs-mcp)
  2. Build the project: npm run build
  3. Publish: npm publish

Updating Documentation URLs

The server uses a static database of Next.js documentation URLs. To update or add new documentation URLs, modify the NEXTJS_DOCS_DATABASE object in src/index.ts. The database is organized by categories and contains 200+ documentation pages covering:

  • Getting Started guides
  • Routing (App Router & Pages Router)
  • Data Fetching patterns
  • API Routes
  • Deployment guides
  • Performance optimization
  • Guides and best practices

The static approach ensures fast response times and no external dependencies.

License

MIT License

Contributing

Contributions are welcome! Please feel free to submit pull requests or open issues for any improvements.

Alternatives

Related Skills

Browse all skills
ui-design-system

UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration.

18
api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

4
openai-knowledge

Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.

4
nextjs-developer

Expert Next.js developer mastering Next.js 14+ with App Router and full-stack features. Specializes in server components, server actions, performance optimization, and production deployment with focus on building fast, SEO-friendly applications.

188
technical-writer

Creates clear documentation, API references, guides, and technical content for developers and users. Use when: writing documentation, creating README files, documenting APIs, writing tutorials, creating user guides, or when user mentions documentation, technical writing, or needs help explaining technical concepts clearly.

8
smithery-mcp-deployment

Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment

7