Skip to content

Conversation

@gaojude
Copy link
Contributor

@gaojude gaojude commented Oct 25, 2025

  • Clarifies that users only need to install next-devtools-mcp - the built-in MCP endpoint is an implementation detail.
  • Reduces confusion by removing the "two servers" framing and moving architecture details to a "How it works" section.
  • Also adds note that capabilities are actively expanding.

@ijjk ijjk added created-by: Next.js team PRs by the Next.js team. Documentation Related to Next.js' official documentation. labels Oct 25, 2025
title: Enabling Next.js MCP Server for Coding Agents
nav_title: Next.js MCP Server
description: Learn how to enable the experimental Next.js MCP server to allow agents access to your application state
description: Learn how to use Next.js MCP support to allow coding agents access to your application state
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uff I guess we didn't want to release this with the experimental name on it - good catch

@gaojude gaojude merged commit 69e1989 into canary Oct 27, 2025
76 checks passed
@gaojude gaojude deleted the jude/clarify-mcp-doc branch October 27, 2025 15:13
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

created-by: Next.js team PRs by the Next.js team. Documentation Related to Next.js' official documentation. locked

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants