π The fast, Pythonic way to build MCP servers and clients.
docs: route SDK v1 users to correct upgrade guide (#5372)
Aritejh Goil361e43b7f34d
diff --git a/docs/getting-started/upgrading/from-fastmcp-3.mdx b/docs/getting-started/upgrading/from-fastmcp-3.mdxindex f999cc1c1..0d08f7bb6 100644--- a/docs/getting-started/upgrading/from-fastmcp-3.mdx+++ b/docs/getting-started/upgrading/from-fastmcp-3.mdx@@ -11,6 +11,10 @@ FastMCP 4 absorbs almost all of this for you. Field access is bridged so your exThe sections below cover what FastMCP handles for you, the changes you must make in your own code, the surfaces removed outright in 4.0, the behavior shifts that compile fine but act differently, and the deprecation timeline for the compatibility shims.+<Note>+If your server imports `FastMCP` from `mcp.server.fastmcp`, it is using FastMCP 1.0 from MCP SDK v1, not standalone FastMCP 3 β even if the `fastmcp` 3.x package is installed. Follow [Upgrading from MCP SDK v1](/getting-started/upgrading/from-mcp-sdk-v1), which changes the import to `from fastmcp import FastMCP` and moves `host` and `port` from `FastMCP(...)` to `mcp.run(transport="http", ...)`.+</Note>+## Install FastMCP 4FastMCP 4 is a stable release:@@ -35,6 +39,9 @@ FIRST, fetch https://gofastmcp.com/getting-started/upgrading/from-fastmcp-3 βThen search the provided code for each signal below. Most FastMCP 3 servers upgrade untouched, so report only what you actually find.+WRONG STARTING VERSION+- `from mcp.server.fastmcp import FastMCP` means the server uses FastMCP 1.0 from MCP SDK v1, not standalone FastMCP 3. Stop and use https://gofastmcp.com/getting-started/upgrading/from-mcp-sdk-v1 instead; that guide also covers `host` and `port` passed to `FastMCP(...)`.+ENVIRONMENT- a pydantic pin below 2.12- a FastAPI pin below 0.133.0, the first release admitting Starlette 1.x (earlier ones cap it, e.g. 0.115.12 requires `starlette<0.47.0`), or any direct Starlette pin below 1.0.1