Next.js DevTools
Next.js development tools MCP server with stdio transport
Official
Published from the GitHub organization vercel, whose domain GitHub verified.
- Registry name
io.github.vercel/next-devtools-mcp- Version
- 0.3.6
- Transports
- stdio
- Packages
- npm
next-devtools-mcp - Repository
- github.com/vercel/next-devtools-mcp
- First published
- Dec 5, 2025
- Updated
- Dec 5, 2025
GitHub stars · Downloads
as of Oct 4, 2026- GitHub stars
- 822
- npm downloads
- 476,294 last month
Add it to a client
Commands and config follow each client’s own MCP docs. Some servers also need an API key or environment variables; see the server’s documentation.
Cursor
mcp.json {
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
} Format from Cursor’s docsGemini CLI
settings.json {
"mcpServers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
} Format from Gemini CLI’s docsVS Code
.vscode/mcp.json {
"servers": {
"next-devtools": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp"
]
}
}
} Format from VS Code’s docsClient compatibility
By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.
- Claude Code Transport supported
- Codex Transport supported
- Cursor Transport supported
- Gemini CLI Transport supported
- VS Code Client docs don’t list transports
- ChatGPT No shared transport
- Claude Client docs don’t list transports
- Cline Transport supported
- Devin Desktop Transport supported
- GitHub Copilot Client docs don’t list transports
- JetBrains AI Assistant Transport supported
- Kiro Transport supported
- OpenCode Client docs don’t list transports
- Zed Client docs don’t list transports
Sources
- Official MCP Registry registry.modelcontextprotocol.io · checked Sep 28, 2026
- GitHub organization vercel (verified domain) github.com · checked Sep 28, 2026
This data comes from the Official MCP Registry.