Add initialization tool for Next.js MCP #79
Merged
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.
Add initialization tool for Next.js MCP
The problem
Calling the initialization tool significantly improves MCP usage throughout the session.
It's unfortunate that we have to explicitly initialize Next.js MCP, but this is the most reliable workaround we've found. We tried automatic context injection using strong descriptions in the tool metadata, but that turned out to be very unreliable.
What this does
Adds an
inittool that sets proper context at the start of a session. The main thing it does is establish thatnextjs_docsmust be used for ALL Next.js-related queries. It also documents the available tools and provides some best practices.Why it matters
Without initialization:
With initialization:
Same with questions like "What's a Client Component?", "How does caching work?", etc. The AI will actually use the tools instead of guessing.