π The fast, Pythonic way to build MCP servers and clients.
docs: drop prerelease install framing from installation and SDK migration guides (#4963)
nate nowack4f33763e4022
diff --git a/docs/getting-started/installation.mdx b/docs/getting-started/installation.mdxindex 6707b991c..8e8078f65 100644--- a/docs/getting-started/installation.mdx+++ b/docs/getting-started/installation.mdx@@ -17,10 +17,6 @@ Or with pip:pip install fastmcp```-<Note>-**FastMCP 4 is in prerelease.** The commands above install the latest stable release, which is still 3.x. To get v4, pin the beta explicitly with `pip install "fastmcp==4.0.0b4"`, or see [Install the v4 Prerelease](/getting-started/upgrading/from-fastmcp-3#install-the-v4-prerelease) for the uv constraint you'll need.-</Note>-### Optional DependenciesFastMCP provides optional extras for specific features. For example, to install the background tasks extra:@@ -44,7 +40,7 @@ You should see output like the following:```bash$ fastmcp version-FastMCP version: 4.0.0b4+FastMCP version: 4.0.0MCP version: 2.0.0Python version: 3.12.2Platform: macOS-15.3.1-arm64-arm-64bit@@ -115,7 +111,7 @@ FastMCP follows semantic versioning with pragmatic adaptations for the rapidly eFor production use, always pin to exact versions:```-fastmcp==4.0.0b4 # Good - an exact version+fastmcp==4.0.0 # Good - an exact versionfastmcp>=4.0.0 # Bad - may install breaking changes```diff --git a/docs/getting-started/upgrading/from-low-level-sdk-v1.mdx b/docs/getting-started/upgrading/from-low-level-sdk-v1.mdxindex 45dc05c73..48803f77d 100644--- a/docs/getting-started/upgrading/from-low-level-sdk-v1.mdx+++ b/docs/getting-started/upgrading/from-low-level-sdk-v1.mdx@@ -81,13 +81,13 @@ For each item found, show the original code, say what it did, and give the FastM## Install-FastMCP 4 is in prerelease, so pin the exact version rather than installing unqualified β a bare `pip install fastmcp` resolves to the latest *stable* release, which today is FastMCP 3:+FastMCP 4 is a stable release:```bash-pip install "fastmcp==4.0.0b4"+pip install "fastmcp>=4"```-An exact pip pin installs even though it's a prerelease; it does not need `--pre`. uv also needs an explicit constraint for the transitive `fastmcp-slim` prerelease, so follow [Install the v4 Prerelease](/getting-started/upgrading/from-fastmcp-3#install-the-v4-prerelease) for a reproducible uv setup.+The `fastmcp` package depends on `fastmcp-slim` at the same version; both resolve together with no extra constraints.FastMCP depends on the `mcp` package, so the SDK stays installed. FastMCP 4 builds on SDK v2, where the protocol types live in a standalone `mcp_types` package that stays importable as `mcp.types`. Most of your `mcp.types` imports disappear entirely in the rewrite below, since FastMCP derives the protocol types from your function signatures.diff --git a/docs/getting-started/upgrading/from-low-level-sdk-v2.mdx b/docs/getting-started/upgrading/from-low-level-sdk-v2.mdxindex 6db5329b1..0cfaca684 100644--- a/docs/getting-started/upgrading/from-low-level-sdk-v2.mdx+++ b/docs/getting-started/upgrading/from-low-level-sdk-v2.mdx@@ -66,13 +66,13 @@ For each item found, show the original code, say what it did, and give the FastM## Install-FastMCP 4 is in prerelease, so pin the exact version rather than installing unqualified β a bare `pip install fastmcp` resolves to the latest *stable* release, which today is FastMCP 3:+FastMCP 4 is a stable release:```bash-pip install "fastmcp==4.0.0b4"+pip install "fastmcp>=4"```-An exact pip pin installs even though it's a prerelease; it does not need `--pre`. uv also needs an explicit constraint for the transitive `fastmcp-slim` prerelease, so follow [Install the v4 Prerelease](/getting-started/upgrading/from-fastmcp-3#install-the-v4-prerelease) for a reproducible uv setup.+The `fastmcp` package depends on `fastmcp-slim` at the same version; both resolve together with no extra constraints.FastMCP 4 depends on the MCP SDK v2 you are already using, so `mcp_types` stays importable and every protocol type keeps its current name and fields. Most of those imports vanish from your code anyway β FastMCP derives them β but the ones you keep need no changes.diff --git a/docs/getting-started/upgrading/from-mcp-sdk-v1.mdx b/docs/getting-started/upgrading/from-mcp-sdk-v1.mdxindex 19b74a3d6..84f792664 100644--- a/docs/getting-started/upgrading/from-mcp-sdk-v1.mdx+++ b/docs/getting-started/upgrading/from-mcp-sdk-v1.mdx@@ -51,13 +51,13 @@ If you have already moved to SDK v2 and write against `MCPServer` today, see [Up## Install-FastMCP 4 is in prerelease, so pin the exact version rather than installing unqualified β a bare `pip install fastmcp` resolves to the latest *stable* release, which today is FastMCP 3:+FastMCP 4 is a stable release:```bash-pip install "fastmcp==4.0.0b4"+pip install "fastmcp>=4"```-An exact pip pin installs even though it's a prerelease; it does not need `--pre`. uv also needs an explicit constraint for the transitive `fastmcp-slim` prerelease, so follow [Install the v4 Prerelease](/getting-started/upgrading/from-fastmcp-3#install-the-v4-prerelease) for a reproducible uv setup.+The `fastmcp` package depends on `fastmcp-slim` at the same version; both resolve together with no extra constraints.FastMCP depends on the `mcp` package, so the SDK stays installed and importable. What changes is which parts of it you reach for. FastMCP 4 builds on SDK v2, where `mcp.server.fastmcp` is gone β anything you imported from it needs a new home, and the sections below cover that. `mcp.types` still resolves (it aliases the standalone `mcp_types` package), though its fields are snake_case now. Update your import, run your server, and if your tools work, you're done.diff --git a/docs/getting-started/upgrading/from-mcp-sdk-v2.mdx b/docs/getting-started/upgrading/from-mcp-sdk-v2.mdxindex 8cd258c03..0df190b55 100644--- a/docs/getting-started/upgrading/from-mcp-sdk-v2.mdx+++ b/docs/getting-started/upgrading/from-mcp-sdk-v2.mdx@@ -91,13 +91,13 @@ For each item found, show the original code, name what changed, and give the Fas## Install-FastMCP 4 is in prerelease, so pin the exact version rather than installing unqualified β a bare `pip install fastmcp` resolves to the latest *stable* release, which today is FastMCP 3:+FastMCP 4 is a stable release:```bash-pip install "fastmcp==4.0.0b4"+pip install "fastmcp>=4"```-An exact pip pin installs even though it's a prerelease; it does not need `--pre`. uv also needs an explicit constraint for the transitive `fastmcp-slim` prerelease, so follow [Install the v4 Prerelease](/getting-started/upgrading/from-fastmcp-3#install-the-v4-prerelease) for a reproducible uv setup.+The `fastmcp` package depends on `fastmcp-slim` at the same version; both resolve together with no extra constraints.FastMCP 4 depends on the MCP SDK v2, so nothing you already import from `mcp_types` moves. That is the practical benefit of migrating at this version rather than an earlier one: you and FastMCP are on the same protocol layer, with the same snake_case field names and the same type package, so the migration touches only the server API.