MCP Tools DirectoryAbout this integration
Next.js development tools MCP server with stdio transport
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.3.6
- Package
- next-devtools-mcp
- Last compatibility test
- Not independently tested
Connect your agent
next-devtools-mcpPublisher README and package manifest reviewed. The documentation says local discovery needs no configuration but does not explicitly define an authentication scheme, so authentication remains unknown. Anonymous usage telemetry is documented and can be disabled. The package was not executed or independently security-audited.
Capabilities: Discover local Next.js 16+ development servers, Proxy runtime error, route, log, metadata, and Server Action tools, Point agents to installed Next.js documentation and browser tooling
Connected profiles
Additional details
io.github.vercel/next-devtools-mcp
Source ↗ · Checked 2026-09-170.3.6
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17next-devtools-mcp
Source ↗ · Checked 2026-09-200.4.1
Source ↗ · Checked 2026-09-20The MCP client launches a local stdio connector that automatically discovers and proxies running Next.js 16+ development servers.
Source ↗ · Checked 2026-09-20The publisher states that local discovery connects automatically with no configuration, but does not explicitly state an authentication mechanism; catalog authentication and setup remain unknown.
Source ↗ · Checked 2026-09-20Run npx -y next-devtools-mcp@latest from the MCP client configuration; runtime tools also require a running Next.js 16+ development server.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20