mirror of
https://github.com/PrefectHQ/fastmcp.git
synced 2026-08-28 02:10:38 +02:00
Restructure docs navigation: CLI section, Composition, More (#3361)
* WIP: Move mounting docs to servers/composition, remove deprecated import_server content * WIP: Add CLI section under More, move testing to Features, restructure nav * WIP: Rename querying to client, remove factory functions from CLI overview * WIP: Promote CLI to top-level section, move Upgrading to More * WIP: Rename CLI installing page to install-mcp * WIP * Add Google Gemini sampling handler docs, fix version badges
This commit is contained in:
Jeremiah Lowin
GitHub
parent
8a356ad870
commit
8bc31360e8
21 changed files with 1020 additions and 163 deletions
|
|
@ -62,15 +62,17 @@ Alternatively, wait for the stable v5 release. See [this issue](https://github.c
|
|||
</Info>
|
||||
## Upgrading
|
||||
|
||||
### From FastMCP 2.x
|
||||
### From FastMCP 2.0
|
||||
|
||||
See the [Upgrade Guide](/getting-started/upgrading/from-fastmcp-2) for a complete list of breaking changes and migration steps.
|
||||
|
||||
### From FastMCP 1.0 (in the Low-Level SDK)
|
||||
### From the MCP SDK
|
||||
|
||||
If you're using FastMCP 1.0 via the `mcp` package (`from mcp.server.fastmcp import FastMCP`), upgrading is straightforward — for most servers, it's a single import change. See the [full upgrade guide](/getting-started/upgrading/from-mcp-sdk) for details.
|
||||
#### From FastMCP 1.0
|
||||
|
||||
### From the Low-Level Server API
|
||||
If you're using FastMCP 1.0 via the `mcp` package (meaning you import FastMCP as `from mcp.server.fastmcp import FastMCP`), upgrading is straightforward — for most servers, it's a single import change. See the [full upgrade guide](/getting-started/upgrading/from-mcp-sdk) for details.
|
||||
|
||||
#### From the Low-Level Server API
|
||||
|
||||
If you built your server directly on the `mcp` package's `Server` class — with `list_tools()`/`call_tool()` handlers and hand-written JSON Schema — see the [migration guide](/getting-started/upgrading/from-low-level-sdk) for a full walkthrough.
|
||||
|
||||
|
|
@ -86,18 +88,6 @@ fastmcp>=3.0.0 # Bad - may install breaking changes
|
|||
|
||||
See the full [versioning and release policy](/development/releases#versioning-policy) for details on our public API, deprecation practices, and breaking change philosophy.
|
||||
|
||||
### Looking Ahead: FastMCP 4.0
|
||||
|
||||
The MCP Python SDK v2 is expected in early 2026 and will include breaking changes. When released, FastMCP will incorporate these upstream changes in a new major version (FastMCP 4.0).
|
||||
|
||||
To avoid unexpected breaking changes, we recommend pinning your dependency with an upper bound:
|
||||
|
||||
```
|
||||
fastmcp>=3.0,<4
|
||||
```
|
||||
|
||||
We'll provide migration guidance when FastMCP 4.0 is released.
|
||||
|
||||
## Contributing to FastMCP
|
||||
|
||||
Interested in contributing to FastMCP? See the [Contributing Guide](/development/contributing) for details on:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ title: Upgrading from FastMCP 2
|
|||
sidebarTitle: "From FastMCP 2"
|
||||
description: Migration instructions for upgrading between FastMCP versions
|
||||
icon: up
|
||||
tag: NEW
|
||||
---
|
||||
|
||||
This guide covers breaking changes and migration steps when upgrading FastMCP.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ title: Upgrading from the MCP Low-Level SDK
|
|||
sidebarTitle: "From MCP Low-Level SDK"
|
||||
description: Upgrade your MCP server from the low-level Python SDK's Server class to FastMCP
|
||||
icon: up
|
||||
tag: NEW
|
||||
---
|
||||
|
||||
If you've been building MCP servers directly on the `mcp` package's `Server` class — writing `list_tools()` and `call_tool()` handlers, hand-crafting JSON Schema dicts, and wiring up transport boilerplate — this guide is for you. FastMCP replaces all of that machinery with a declarative, Pythonic API where your functions *are* the protocol surface.
|
||||
|
|
@ -583,11 +582,11 @@ if __name__ == "__main__":
|
|||
|
||||
Once you've upgraded, you have access to everything FastMCP provides beyond the basics:
|
||||
|
||||
- **[Server composition](/servers/providers/mounting)** — Mount sub-servers to build modular applications
|
||||
- **[Server composition](/servers/composition)** — Mount sub-servers to build modular applications
|
||||
- **[Middleware](/servers/middleware)** — Add logging, rate limiting, error handling, and caching
|
||||
- **[Proxy servers](/servers/providers/proxy)** — Create a proxy to any existing MCP server
|
||||
- **[OpenAPI integration](/integrations/openapi)** — Generate an MCP server from an OpenAPI spec
|
||||
- **[Authentication](/servers/auth/authentication)** — Built-in OAuth and token verification
|
||||
- **[Testing](/patterns/testing)** — Test your server directly in Python without running a subprocess
|
||||
- **[Testing](/servers/testing)** — Test your server directly in Python without running a subprocess
|
||||
|
||||
Explore the full documentation at [gofastmcp.com](https://gofastmcp.com).
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@ title: Upgrading from the MCP SDK
|
|||
sidebarTitle: "From MCP SDK"
|
||||
description: Upgrade from FastMCP in the MCP Python SDK to the standalone FastMCP framework
|
||||
icon: up
|
||||
tag: NEW
|
||||
---
|
||||
|
||||
If your server starts with `from mcp.server.fastmcp import FastMCP`, you're using FastMCP 1.0 — the version bundled with v1 of the `mcp` package. Upgrading to the standalone FastMCP framework is easy. **For most servers, it's a single import change.**
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue