Developer tools · MCP server
Next devtools MCP: MCP server, setup and security
Next devtools MCP is an MCP server published on GitHub that lets an AI agent diagnose Next.js runtime issues, inspect routes and consult upgrade guides. Its repository has 832 stars and its last commit is from September 15, 2026, but it declares no licence.
What Next devtools MCP does
According to its repository: “Next.js runtime diagnostics, route inspection, dev server logs, docs search and upgrade guides for coding agents.”
An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Next devtools MCP is listed under Developer tools, a category of 475 servers in the directory, where it ranks #43 by stars.
Topics declared by the repository: next-devtools, nextjs, coding-agents.
Installing and connecting Next devtools MCP
Distribution modes declared in the official MCP registry:
- npm package (Node.js, usually started with
npx)
Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript.
Security: what to check
An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.
Points found for Next devtools MCP:
- No licence: without a licence the code is not legally reusable, even if it is public. Avoid it in a company setting without the author's agreement.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on October 13, 2025, the vercel/next-devtools-mcp repository has 832 stars and 66 forks, with 10 open issues. It has more stars than 91% of the servers in the directory. Last change 1 month ago. Version published in the registry: 0.3.6 (December 5, 2025).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Next devtools MCP is a reasonable choice; check the points below before connecting it.
Strengths
- Maintained by the service's own vendor
- Active project: recent commit
- Widely followed: 832 stars
- Listed in the official MCP registry
Limitations
- No licence declared
Avoid if…
- Company use without the author's agreement
Alternatives
- Radar Kubernetes MCP Server3.9K ★
- Repowise7.9K ★
- Jscpd6.4K ★
- Apify MCP server12.9K ★
- Codebase Memory47.4K ★
- PostHog MCP Server40.4K ★
Learn more
Frequently asked questions
How do I install Next devtools MCP?
Next devtools MCP is distributed as npm package (Node.js, usually started with npx). Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of vercel/next-devtools-mcp.
Is Next devtools MCP free?
The code is public but has no declared licence: it is not formally free to reuse.
Is Next devtools MCP safe?
Points to watch: no licence. Give it minimum rights and approve sensitive actions.
Is it an official server?
Yes: the awesome-mcp-servers list marks it as the service vendor's official implementation.
What are the alternatives to Next devtools MCP?
In the same category: Radar Kubernetes MCP Server, Repowise, Jscpd, and Apify MCP server. Radar Kubernetes MCP Server and Repowise score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score