Fix v2 upgrade guide: remove incorrect v1 import advice#3226
Merged
Conversation
marvin-context-protocol
Bot
added
the
documentation
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
1 participant
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.
The "Upgrading from FastMCP 2" guide opened by telling v2 users to swap
from mcp.server.fastmcp import FastMCPforfrom fastmcp import FastMCP— an import change that only applies to v1/MCP SDK users (already covered in the other guide). FastMCP 2 users have always usedfrom fastmcp import FastMCP.Removed the bogus import migration step from both the prose and the embedded LLM prompt, and reframed the opening to accurately describe what v2→v3 actually touches: deprecated constructor kwargs, sync-to-async shifts, and renamed methods.