MCP server
by nanameru
Access organized Next.js documentation on routing, API routes, deployment & more. Find the latest Next.js doc resources
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.
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.
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.
MIT
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.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Next.js Documentation reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: Next.js Documentation is the kind of server we cite when onboarding engineers to host + tool permissions.
Next.js Documentation reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Next.js Documentation for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
I recommend Next.js Documentation for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Next.js Documentation surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend Next.js Documentation for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Next.js Documentation surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: Next.js Documentation surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Next.js Documentation is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 26
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.
npx from any MCP clientStandard 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
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
</details>
<details>
<summary>Claude Desktop</summary>
Follow the MCP install guide and use the standard config above.
</details> <details> <summary>Cursor</summary>Go to Cursor Settings → MCP → Add new MCP Server.
Use the following:
Add via CLI:
code --add-mcp '{"name":"nextjs-docs-mcp","command":"npx","args":["@taiyokimura/nextjs-docs-mcp@latest"]}'
Or use the install links above.
</details> <details> <summary>LM Studio</summary>Add MCP Server with:
Advanced settings → Extensions → Add custom extension:
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
}
}
}
</details>
<details>
<summary>Qodo Gen</summary>
Open Qodo Gen → Connect more tools → + Add new MCP → Paste the standard config above → Save.
</details> <details> <summary>Windsurf</summary>Follow Windsurf MCP documentation and use the standard config above.
</details>Get all Next.js documentation URLs for AI agents to analyze and select relevant ones.
Parameters:
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:
{
"tool": "get_all_docs"
}
get_all_docs# 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.
npm run build
package.json to your scope (e.g., @taiyokimura/nextjs-docs-mcp)npm run buildnpm publishThe 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:
The static approach ensures fast response times and no external dependencies.
MIT License
Contributions are welcome! Please feel free to submit pull requests or open issues for any improvements.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.