next-devtools-mcp
next-devtools-mcp is an MCP server published by Vercel, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Vercel. Last verified 2026-08-20.
Does next-devtools-mcp support the current MCP specification (2026-07-28)?
Not yet confirmed. next-devtools-mcp is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is next-devtools-mcp a first-party (official) MCP server?
Yes. next-devtools-mcp is the first-party MCP server published by Vercel (last verified 2026-08-20).
How do I connect to next-devtools-mcp?
next-devtools-mcp is available via the package npm:next-devtools-mcp, the official MCP Registry under io.github.vercel/next-devtools-mcp, the source repository at https://github.com/vercel/next-devtools-mcp. Authentication: unknown. Transports: stdio.
Does next-devtools-mcp support MCP revision 2026-07-28?
No. next-devtools-mcp was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
Does next-devtools-mcp support MCP revision 2025-11-25?
Yes. next-devtools-mcp supports MCP revision 2025-11-25 (checked 2026-08-20).
When were next-devtools-mcp's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Next.js development tools MCP server with stdio transport
Which MCP spec revisions does next-devtools-mcp support?
next-devtools-mcp has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2026-07-28 | Not supported | Source | |
| MCP 2025-11-25 | Supported | Source |
How widely adopted is next-devtools-mcp?
Ranked #26 in The MCP 500 with Adoption Index 66.87 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 72,601 | API · |
| GitHub stars | 821 | API · |
| GitHub forks | 65 | API · |
| Last push | 2026-09-15T00:32:28Z | API · |
| Repository archived | no | API · |
Repository and package signals for next-devtools-mcp
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 9
- Primary language
- TypeScript
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: coding-agents, mcp, mcp-server, next-devtools, nextjs — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.4.0- Last published
- First published
- Releases
- 35
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 5
- Unpacked size
- 65 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.vercel/next-devtools-mcp at version 0.3.6 - lists package npm:next-devtools-mcp and repository https://github.com/vercel/next-devtools-mcp - accessed
- GitHub organization vercel (vercel.com) hosts next-devtools-mcp (807 stars); the server fronts Next.js development, Vercel's own framework - accessed
- GitHub organization vercel, retrieved 2026-08-20 - name "Vercel", blog https://vercel.com, type Organization, is_verified true; confirms the io.github.vercel registry namespace belongs to the Vercel company record rather than to a separate community account - accessed
- npm registry metadata for next-devtools-mcp at published version 0.4.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.25.2 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.25.2, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed