docs: update MCP guides for the thin next-devtools-mcp#94859
Open
gaojude wants to merge 1 commit into
Open
Conversation
The next-devtools-mcp knowledge-base and migration tools are being replaced by the docs Next.js bundles in node_modules/next/dist/docs/ and by the upgrade codemod. Update the MCP guide capabilities and the v16 upgrade guide to describe the docs gateway, runtime diagnostics, and codemod-based upgrades instead of the removed knowledge-base/upgrade/cache-components tools.
Contributor
Tests PassedCommit: 9c37a35 |
Contributor
Stats skippedCommit: 9c37a35 |
icyJoseph
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the Next.js docs that describe
next-devtools-mcpto match its 0.4.0 thin-connector shape (see vercel/next-devtools-mcp#145). The knowledge-base, migration/upgrade, and Cache Components tools are gone — docs now ship with Next.js innode_modules/next/dist/docs/and upgrades use the codemod — so the guides should no longer point agents at those tools.In the MCP guide (
mcp.mdx), the Development Tools list drops "Knowledge Base", "Migration and Upgrade Tools", and "Caching Guide" in favor of a documentation gateway that points agents at the bundled docs, and the examples now describe reading bundled docs and running the codemod rather than querying a knowledge base. In the v16 upgrade guide, the "Using AI Agents with Next.js DevTools MCP" section no longer instructs users to run removed prompts (Next Devtools, help me upgrade/migrate to cache components); it points to the codemod plus runtime diagnostics.Should land with the next-devtools-mcp 0.4.0 release.