Upgrade a FastMCP Server
- Record the installed
fastmcp,mcp, Python, and deployment versions plus the server's existing component inventory and representative outputs. - Run
bin/mcp-server-upgrade PATHfor a static migration inventory, then read references/upgrade-map.md. - Separate framework migration from product redesign. Preserve observable names, schemas, errors, auth requirements, and effects unless the user requested a breaking change.
- Migrate imports, configuration, composition, context access, and transport setup in small groups. Replace deprecated patterns with current providers, transforms, component authorization, visibility, versioning, storage, or tasks only where they solve an actual requirement.
- Treat Code Mode and Apps as opt-in product capabilities, not automatic upgrade steps.
- Compare pre/post component catalogs and run direct, in-memory, and deployment smoke tests.
Ask agents/migration-reviewer.md to inspect compatibility evidence before release.