| FMRS | 63 / 100 · C | 76 / 100 · B |
|---|
| Reliability | 10 / 20 | 13 / 20 |
|---|
| Security and permissions | 12 / 20 | 14 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 15 / 20 | 14 / 20 |
|---|
| Best for | - Front-end developers on Next.js 16+ who want coding agents to read live dev server state directly
- Teams using MCP-capable agent workflows such as Claude Code, Cursor, or Codex
- Next.js projects that need version-accurate docs instead of fetching docs over the network
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Projects not using Next.js or below version 16 (nextjs_index / nextjs_call need a running Next.js 16+ dev server)
- Users expecting the server to fetch docs itself or drive the browser directly (nextjs_docs and browser_eval are gateways only)
- Deployments needing non-stdio transports such as remote HTTP
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Read the project's next/package.json locally to resolve the installed Next.js version and docs path
- Network access to local dev server ports (e.g. localhost:3000) to discover and call the /_next/mcp endpoint
- Write local files under ~/.next-devtools-mcp/ (telemetry-id, telemetry-salt, and debug log mcp.log)
- browser_eval may prompt installation of a global CLI: npm install -g agent-browser
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - Anonymous usage telemetry is collected by default (tool usage, anonymous error messages, session ID, timestamps, and basic environment such as OS and Node.js version); your code, file contents or paths, personal data, credentials, and tool arguments are not collected. Opt out with export NEXT_TELEMETRY_DISABLED=1, and delete local telemetry data with rm -rf ~/.next-devtools-mcp.
- Upstream requests for runtime tool calls, including response-body reads, have a 60-second deadline.
- nextjs_docs falls back to https://nextjs.org/docs when an installed release has no bundled docs and asks the agent to verify APIs against the installed version.
- Using next-devtools-mcp@latest keeps clients on the latest version, which may introduce unexpected changes.
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Code, Cursor, Codex, Amp, Gemini, Antigravity, VS Code, Warp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 4 | 15 |
|---|