Next.js 16+ includes MCP (Model Context Protocol) server support that connects coding agents (Claude, Cursor) to your running dev server per the official docs. The agent gets real-time access to app internals - routes, errors, component tree. The team that uses Next.js MCP has AI-assisted debugging and code understanding.
Table of contents
- What is MCP
- Enabling MCP in Next.js
- Connect Claude or Cursor
- What the agent can do
- Security
- Use cases
- FAQ
What is MCP
Model Context Protocol (MCP) is an open standard for connecting AI models to data sources and tools. Next.js implements an MCP server that exposes app internals to MCP clients (Claude, Cursor, etc.).
Enabling MCP in Next.js
On Next.js 16+:
// next.config.js
module.exports = {
experimental: {
mcp: true,
},
};Then next dev exposes MCP. The team that has Next.js 16+ has MCP support built-in.
Connect Claude or Cursor
In Claude Desktop config (~/.config/claude_desktop_config.json):
{
"mcpServers": {
"nextjs": {
"command": "npx",
"args": ["-y", "@next/mcp-client", "--url", "http://localhost:3000/_next/mcp"]
}
}
}The team that has Claude can connect to the Next.js dev server’s MCP endpoint.
What the agent can do
With MCP, the agent can:
- List all routes and their props.
- Read server component state.
- See current errors and stack traces.
- Navigate the component tree.
- Inspect build output.
The team that uses this has AI that understands the running app, not just source code.
Security
MCP exposes dev server internals. Only run in dev, never in production. The team that exposes MCP in production has a security incident.
Use network isolation (localhost only) and don’t expose the dev server publicly.
Use cases
- Debugging: AI reads error + stack trace + relevant component.
- Code understanding: AI navigates the actual app, not just source.
- Refactoring: AI sees all usages of a component in the running app.
- Testing: AI runs queries against the dev server to verify behavior.
FAQ
Is Next.js MCP stable?
Yes on Next.js 16+ (released 2025). The team that uses it on Next 16+ has stable MCP.
Which coding agents work with Next.js MCP?
Any MCP client - Claude Desktop, Cursor, Cline, custom. The team that uses Claude or Cursor has direct integration.
Can I use MCP for production debugging?
No - MCP is dev-only by design. For production debugging, use observability tools (Datadog, Sentry, OpenTelemetry).
Does MCP add runtime overhead?
Only in dev mode. Production builds don’t include MCP code. The team that has MCP enabled has no prod impact.
Can I extend the MCP server with my own tools?
Yes - Next.js MCP supports custom tools via the @next/mcp-server SDK. The team that builds custom tools has full extensibility.
If you are sizing the infrastructure for the kind of project this post covers, the RunxBuild hosting calculator is the right place to model the line items. The compute, the memory, the storage, the bandwidth, the database - each one is a separate number, and the team’s mental model for the platform is the sum of those numbers. The RunxBuild dashboard is where the team sees the actual usage in one place.
Useful related references: